https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082012-01-25T15:29:17ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #2280: starting X reboots the machinehttps://bugs.dragonflybsd.org/issues/2280?journal_id=105562012-01-25T15:29:17Zphma
<ul></ul>Here's the output of "git show", so that you can get the same version:
<ol>
<li>git show<br />commit 4f45907333eb0ca7cda1d2633ecdf1010f359919<br />Author: Sepherosa Ziehau <<a class="email" href="mailto:sephe@dragonflybsd.org">sephe@dragonflybsd.org</a>><br />Date: Tue Jan 17 16:52:36 2012 +0800</li>
</ol>
<pre><code>msix/pci: Enable MSI-X by default</code></pre>
<p>diff --git a/sys/bus/pci/pci.c b/sys/bus/pci/pci.c<br />index d93b6aa..063f169 100644<br />--- a/sys/bus/pci/pci.c<br />+++ b/sys/bus/pci/pci.c<br /><code>@ -296,12 +296,10 </code>@ TUNABLE_INT("hw.pci.enable_msi", &pci_do_msi);<br /> SYSCTL_INT(_hw_pci, OID_AUTO, enable_msi, CTLFLAG_RW, &pci_do_msi, 1,<br /> "Enable support for MSI interrupts");</p>
<p><del>static int pci_do_msix = 0;<br /></del>#if 0<br />+static int pci_do_msix = 1;<br /> TUNABLE_INT("hw.pci.enable_msix", &pci_do_msix);<br /> SYSCTL_INT(_hw_pci, OID_AUTO, enable_msix, CTLFLAG_RW, &pci_do_msix, 1,<br /> "Enable support for MSI-X interrupts");<br />-#endif</p>
<pre><code>static int pci_honor_msi_blacklist = 1;<br /> TUNABLE_INT("hw.pci.honor_msi_blacklist", &pci_honor_msi_blacklist);</code></pre> DragonFlyBSD - Bug #2280: starting X reboots the machinehttps://bugs.dragonflybsd.org/issues/2280?journal_id=105652012-01-27T05:42:15Zphma
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p>I am now running v3.1.0.52.g42a0e-DEVELOPMENT. Romick advised me to turn off DRI in xorg.conf if I'm running the Intel driver. I did, and I can log into X, but Kwin says that desktop effects are too slow and turns them off. I turned DRI back on and restarted X. The computer rebooted, then hung when it got to the X server. I booted in single-user mode, couldn't figure out how to edit without the terminal codes working, mounted -a, started sshd, and shelled in from my other box and turned DRI off again.</p>
<p>I am upping the priority because the bug is in both 2.13 and 3.1, so it's probably in 3.0 as well. It appeared between v2.11.0.681.g0eed2f-DEVELOPMENT and v2.13.0.957.g4f459-DEVELOPMENT</p> DragonFlyBSD - Bug #2280: starting X reboots the machinehttps://bugs.dragonflybsd.org/issues/2280?journal_id=105732012-01-28T20:31:54Zc.turner1
<ul></ul><p>On 01/26/12 23:42, Pierre Abbat via Redmine wrote:</p>
<blockquote>
<p>I am now running v3.1.0.52.g42a0e-DEVELOPMENT. Romick advised me to turn off DRI in xorg.conf</p>
</blockquote>
<p>For refs - am also having the same issue with intel driver on an asus eee901<br />with day-before-3.0-branch 2.13 - disabling DRI also fixed.</p>
<p>Previously worked OK IIRC but this was a 2.10 install / old pkgsrc<br />FWIW.</p>
<p>This bug should probably be renamed to 'xorg+intel+dri' crashes the machine</p>
<p>The intel driver directly deals with agp(4) from what I can tell,<br />haven't gotten further than that (and likely won't any time soon)</p>
<p>Will see if I can generate a dump over the next few days/weeks,<br />though I think this might not generate one</p> DragonFlyBSD - Bug #2280: starting X reboots the machinehttps://bugs.dragonflybsd.org/issues/2280?journal_id=105752012-01-29T19:12:28Zmasterblaster
<ul></ul><p>I can reproduce the problem too on a i386 machine (Pentium M).<br />On a x86_64 (Intel D510), same Xorg driver (i915), same dfly git version, no problem.</p>
<p>From i386 dmesg, v2.13.0.990.g98bec-DEVELOPMENT:</p>
<p>info: [drm] AGP at 0xe8000000 128MB<br />info: [drm] Initialized i915 1.6.0 20080730<br />panic: lockmgr: LK_RELEASE: no lock held<br />Trace beginning at frame 0xcd337ab8<br />panic(ffffffff,c04d7c40,c0442698,cd337ae8,ff800000) at panic+0x107 0xc01cb7fc<br />panic(c0442698,0,1,0,e87ec000) at panic+0x107 0xc01cb7fc<br />lockmgr(cd300e94,6,c1eaae20,cd337b38,c0354078) at lockmgr+0x492 0xc01bddd1<br />drm_ioctl(cd337b5c,c0477e08,ca6535f0,80186443,cd337c0c) at drm_ioctl+0x356 0xcd34c7ee<br />dev_dioctl(ca6535f0,80186443,cd337c0c,43,c9acc588) at dev_dioctl+0x40 0xc01af508<br />devfs_fo_ioctl(c1efb968,80186443,cd337c0c,c9acc588,cd337cf0) at devfs_fo_ioctl+0x119 0xc0302d00<br />fo_ioctl(c9acc588,cd337cf0,18,1,cd337c54) at fo_ioctl+0x3c 0xc01f5d1d<br />mapped_ioctl(a,80186443,bfbff594,0,cd337cf0) at mapped_ioctl+0x4c9 0xc01f61ff<br />sys_ioctl(cd337cf0,cd337d00,c,cd062858,0) at sys_ioctl+0x2e 0xc01f62ae<br />syscall2(cd337d40) at syscall2+0x232 0xc03e0520<br />Xint0x80_syscall() at Xint0x80_syscall+0x36 0xc03b2eb6<br />Debugger("panic")</p>
<p>Get core from <a class="external" href="https://84.73.12.43/crash/core.0.txz">https://84.73.12.43/crash/core.0.txz</a></p> DragonFlyBSD - Bug #2280: starting X reboots the machinehttps://bugs.dragonflybsd.org/issues/2280?journal_id=105862012-02-01T21:43:15Zdillon
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>I tracked down the ioctl from the dump and there was an obviously missing DRM_LOCK() in an UNLOCK/LOCK sequence. The bug fix has been committed to master and MFC'd to the release. 7ca5621f78805fd7285a61178d2b25a768715c2f (master) and b60e3fd0b0654b7103d8a27eabb832ba9cec8edc (release).</p>
<p>-Matt</p> DragonFlyBSD - Bug #2280: starting X reboots the machinehttps://bugs.dragonflybsd.org/issues/2280?journal_id=105872012-02-01T23:30:57Zphma
<ul></ul><p>I just updated my kernel and it is working.</p>