On Monday 14 December 2009 9:37:51 pm Jonathan Chen wrote:
> On Mon, Dec 14, 2009 at 10:46:27AM -0500, John Baldwin wrote:
> > On Sunday 13 December 2009 2:19:05 pm Jonathan Chen wrote:
> > > Hi,
> > >
> > > This is a general rehash of a problem that I've been having with my
> > > Dell Latitude D830 with an nVidia Quadro NVS 140M internal graphics
> > > card. I've been using the XOrg's "vesa" driver ever since something in
the
> > > code rendered the "nvidia" driver inoperable in 7-STABLE sometime mid
> > > last year. With nVidia's new 195.22 (BETA) drivers, I had hoped that I
> > > could bypass the problem. Unfortunately, I seem to be experiencing the
same
> > > problem as described in the following thread:
> > >
> > > http://www.nvnews.net/vbulletin/showthread.php?t=142391
> > >
> > > which appears to be implying that something in the kernel is
> > > interfering with memory allocation. Would it be possible for someone
> > > with deeper kernel-fu be able to take a look at this issue?
> >
> > Do you have a verbose dmesg available?
>
> I've attached a dmesg with a verbose boot. I hope this is what you're
> looking for.
Ok, can you grab the output of 'devinfo -r' and 'devinfo -ur'? I suspect that
when the bridge allocates the prefetch resource range from the parent it is
failing somehow. For a quick hack try something like this:
Index: subr_rman.c
===================================================================
--- subr_rman.c (revision 200359)
+++ subr_rman.c (working copy)
@@ -284,7 +284,7 @@
count, flags,
dev == NULL ? "<null>" : device_get_nameunit(dev)));
want_activate = (flags & RF_ACTIVE);
- flags &= ~RF_ACTIVE;
+ flags &= ~(RF_ACTIVE | RF_PREFETCHABLE);
mtx_lock(rm->rm_mtx);
--
John Baldwin
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
