On Thu, 16 Apr 2009 22:18:36 +0300
Kostik Belousov kostik...@gmail.com wrote:
On Thu, Apr 16, 2009 at 10:47:55AM -0700, Tim Kientzle wrote:
Gary Jennejohn wrote:
deeptec...@gmail.com wrote:
This kernel output really looks bad:
Wai
tSiynngc i(nmga xd is6k0s ,s evcnoonddess) rfeomra
I can reliably (~40%) reproduce a freeze, which I think is related.
Using the GENERIC debug kernel built from SVN HEAD:
# cd /usr/obj/usr/src/sys/GENERIC/
# kgdb kernel.debug /var/crash/vmcore.0
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered
On Thu, 16 Apr 2009 17:04:55 +0200
deeptec...@gmail.com wrote:
[snip a whole bunch of stuff]
This kernel output really looks bad:
Wai
tSiynngc i(nmga xd is6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr0o
cess `syncer' to stop...0 done
I can't speak to the rest, but this is probably
Gary Jennejohn wrote:
deeptec...@gmail.com wrote:
This kernel output really looks bad:
Wai
tSiynngc i(nmga xd is6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr0o
cess `syncer' to stop...0 done
I can't speak to the rest, but this is probably because you have SMP and
don't have `options
On Thu, Apr 16, 2009 at 10:47:55AM -0700, Tim Kientzle wrote:
Gary Jennejohn wrote:
deeptec...@gmail.com wrote:
This kernel output really looks bad:
Wai
tSiynngc i(nmga xd is6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr0o
cess `syncer' to stop...0 done
I can't speak to the rest, but
Kostik Belousov wrote:
On Thu, Apr 16, 2009 at 10:47:55AM -0700, Tim Kientzle wrote:
Gary Jennejohn wrote:
deeptec...@gmail.com wrote:
This kernel output really looks bad:
Wai
tSiynngc i(nmga xd is6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr0o
cess `syncer' to stop...0 done
I can't
Hello.
Just to let everyone know, I'm now coming to the conclusion that
I may be suffering from hardware/thermal problems and that the DRI
driver wasn't actually at fault (but highlighted the problem by
pushing the hardware... harder).
Thanks for the assistance, though.
xw
On Friday 10 April 2009 20:31:33 Robert Noland wrote:
On Fri, 2009-04-10 at 18:59 +0100, xorquew...@googlemail.com wrote:
The system doesn't seem to have frozen since DRI/DRM was disabled.
I did have one crash/reboot whilst building a large number of
packages with tinderbox. I've currently
On 2009-04-11 02:30:40, Paul B. Mahol wrote:
If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
Not doing this will increase drasticaly chances of locking whole system
and not providing any debug data.
I don't seem to have that sysctl.
You sure that's the correct name?
xw
The machine ran for hours, apparently. I ended up going to
bed and leaving it running. Woke up to find it on display
sleep, frozen.
It didn't panic, apparently.
I've included Xorg.0.log and the last few lines of /var/log/messages
but I don't believe they show anything very interesting.
I should
On Sat, 11 Apr 2009 11:15:59 +0100
xorquew...@googlemail.com wrote:
On 2009-04-11 02:30:40, Paul B. Mahol wrote:
If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
Not doing this will increase drasticaly chances of locking whole system
and not providing any debug data.
On Sat, 11 Apr 2009 11:15:59 +0100 xorquew...@googlemail.com wrote:
x On 2009-04-11 02:30:40, Paul B. Mahol wrote:
If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
Not doing this will increase drasticaly chances of locking whole system
and not providing any debug data.
On Sat, 2009-04-11 at 11:23 +0100, xorquew...@googlemail.com wrote:
The machine ran for hours, apparently. I ended up going to
bed and leaving it running. Woke up to find it on display
sleep, frozen.
Are you running the 7.2-PRE or -STABLE? There are a few relevant fixes
in -STABLE that didn't
On 2009-04-11 16:12:45, Mikolaj Golub wrote:
If you are interested in providing useful information about your freezes,
please read the following:
Thanks very much. Will be doing all of the above.
___
freebsd-hackers@freebsd.org mailing list
On 2009-04-11 14:11:15, Robert Noland wrote:
Are you running the 7.2-PRE or -STABLE? There are a few relevant fixes
in -STABLE that didn't make it into the pre-release.
Sorry, should've made that clear. It was meant to be -STABLE but it
seems to be calling itself -PRE. Just to clarify, my
On Sat, 2009-04-11 at 20:30 +0100, xorquew...@googlemail.com wrote:
On 2009-04-11 14:11:15, Robert Noland wrote:
Are you running the 7.2-PRE or -STABLE? There are a few relevant fixes
in -STABLE that didn't make it into the pre-release.
Sorry, should've made that clear. It was meant to
On Sat, 2009-04-11 at 14:06 +0200, Gary Jennejohn wrote:
On Sat, 11 Apr 2009 11:15:59 +0100
xorquew...@googlemail.com wrote:
On 2009-04-11 02:30:40, Paul B. Mahol wrote:
If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
Not doing this will increase drasticaly chances
On 4/11/09, xorquew...@googlemail.com xorquew...@googlemail.com wrote:
On 2009-04-11 02:30:40, Paul B. Mahol wrote:
If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
Not doing this will increase drasticaly chances of locking whole system
and not providing any debug data.
I
Hello.
Recently bought a new system and am experiencing problems with system freezes.
I think the most likely culprit is DRI. The freezes occur apparently at random.
I've disabled drm.ko and radeon.ko and the system doesn't appear to have frozen
yet.
I'm running 7.2-PRERELEASE (STABLE as of
On Fri, 2009-04-10 at 16:42 +0100, xorquew...@googlemail.com wrote:
Hello.
Recently bought a new system and am experiencing problems with system freezes.
I think the most likely culprit is DRI. The freezes occur apparently at
random.
I've disabled drm.ko and radeon.ko and the system
Hello.
On 2009-04-10 12:42:48, Robert Noland wrote:
Are you running powerd by chance? I was seeing an issue that seemed to
be related to powerd. Since I've disabled it on that box, it hasn't
hung up any more.
I'm not running powerd, no.
As far as drm is concerned, I've been running on
On Fri, 2009-04-10 at 18:59 +0100, xorquew...@googlemail.com wrote:
Hello.
On 2009-04-10 12:42:48, Robert Noland wrote:
Are you running powerd by chance? I was seeing an issue that seemed to
be related to powerd. Since I've disabled it on that box, it hasn't
hung up any more.
I'm
On 2009-04-10 13:31:33, Robert Noland wrote:
If it is locking the whole system, then a core is really our best shot.
If you can extract anything useful from xorg.log or setting
hw.dri.0.debug that also might be of use.
I'm running on 2 cores, but it is possible that some locking issue
On 4/10/09, xorquew...@googlemail.com xorquew...@googlemail.com wrote:
On 2009-04-10 13:31:33, Robert Noland wrote:
If it is locking the whole system, then a core is really our best shot.
If you can extract anything useful from xorg.log or setting
hw.dri.0.debug that also might be of use.
24 matches
Mail list logo
