I haven't heard anything on this in three weeks. I filed a bug report, but no
acceptance yet. Does this imply that there is no intention to fix this
problem? What is happening with this? Am I even posting to the right list? I'm
completely in the dark here.
--
David Johnson
? Or should I keep banging my head against the wall?
--
David Johnson
___
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
type drm_bufs leaked memory on
destroy (4 allocations, 128 bytes leaked).
After this I can load the radeon and drm modules, but X will not start,
complaining about no screen found.
--
David Johnson
___
freebsd-stable@freebsd.org mailing list
http
On Tuesday 12 May 2009 08:17:51 am Robert Noland wrote:
On Sat, 2009-05-09 at 18:41 -0700, David Johnson wrote:
On Friday 08 May 2009 03:31:04 pm Robert Noland wrote:
In order to guess what might be causing this, drm debugging needs to be
enabled before the hang, so that we can hopefully
On Tuesday 12 May 2009 11:52:29 am David Johnson wrote:
I may have made a mistake though, and briefly turned on debugging earlier
in the session. I'll get another trace this evening when I have time, to
double check.
Yup, I must have turned on debugging earlier in that session. All I can get
compositing so much that it won't reproduce.
--
David Johnson
___
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
captured early enough to catch some additional information. I've place the
full file online at http://www.usermode.org/misc/dmesg.txt, but am including
some snippets here. Hopefully this is enough to move forward.
--
David Johnson
...
[drm:pid1822:drm_ioctl] pid=1822, cmd=0xc0286429, nr=0x29, dev
on hw.dri.0.debug, and messages quickly filled up with the
following repeated message:
[drm:pid1195:drm_ioctl] returning 4
[drm:pid1195:drm_ioctl] pid=1195, cmd=0x80046457, nr=0x57, dev 0xc615fa00,
auth=1
--
David Johnson
___
freebsd-stable
On Tuesday 05 May 2009 08:41:48 pm David Johnson wrote:
On Monday 04 May 2009 11:20:17 pm Robert Noland wrote:
This generally suggests that the GPU is locked up... Given that you say
sometimes it locks up hard (usually a panic, that you can't see since X
is running) and other times only X
.
What information do you need to go forward, and how do I collect it?
p.s. I didn't have a problem with sources from RELENG_7 date=2009.03.13, if
that helps any.
Thanks for you time,
--
David Johnson
___
freebsd-stable@freebsd.org mailing list
http
/xorg.conf
http://www.usermode.org/misc/Xorg.0.log.old
p.s. Posting to freebsd-stable, as this problem has been previously discussed
here. If this is no longer the appropriate list, please let me know.
Thank you,
--
David Johnson
___
freebsd-stable
On Saturday 28 March 2009 10:45:24 pm David Johnson wrote:
My last email was premature. I hung again while trying to open an image. I
am attaching the output of dmesg, ps and the Xorg log. The latter is full
of the following messages:
Forgot the Xorg log. Here it is:
--
David Johnson
On Saturday 28 March 2009 11:08:49 pm David Johnson wrote:
On Saturday 28 March 2009 10:45:24 pm David Johnson wrote:
My last email was premature. I hung again while trying to open an image.
I am attaching the output of dmesg, ps and the Xorg log. The latter is
full of the following
that you want to checkout. See man csup and reference
the section titled CHECKOUT MODE.
If PCI-Express is not allowed (do they even make AGP boards anymore?) then
I'll have to downgrade until the GART gets fixed.
--
David Johnson
___
freebsd-stable
?
--
David Johnson
___
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
On Saturday 28 March 2009 11:07:49 am Robert Noland wrote:
Ok, the GART should be fixed in HEAD as well...
r190282 is what you need. You probably need 190123 for it to apply
cleanly. I'll attach both.
That appears to work. Half an hour now, and no hang yet.
--
David Johnson
is probably stuck in an infinite loop.
[mi] mieqEnequeue: out-of-order valuator event; dropping.
I can't afford to be a tester, I have work I need to get done with this
system. Please let me know if this gets fixed. In the meantime I'm going back
to older code.
--
David Johnson
Copyright (c) 1992
EXA
EndSection
I have had no prior problems with -STABLE. I have an Intel Q45 chipset, so I
need to run -STABLE, and don't have the option of going back to -RELEASE. Is
there any easy way to go back to an earlier -STABLE?
--
David Johnson
___
freebsd
18 matches
Mail list logo
