System freezes if the kernel package used is gentoo-sources-r2 or r3 (2.6.13.2 or 2.6.13.3 with gentoo patchset) . I don't know if this happends with gentoo-sources-r1 (2.6.13.1) but i assume it does :). The system doesn't freeze if gentoo-sources is used (or vanilla 2.6.13). It happends after 5-10-15 minutes or even more after boot, under normal desktop conditions: browsing, office. Sometimes the system freezes when i close firefox, sometimes when i open nautilus, sometimes when i'm reading my emails. When the system freezes there is no ping reply in it, and i can't do nothing than cold reboot. It is possible that this bug isn't due a kernel bug, but only when using 2.6.13.2 or .3 the system freeze happends. Reproducible: Couldn't Reproduce Steps to Reproduce: All kernels (2.6.13-gentoo, 2.6.13-gentoo-r2, 2.6.13-gentoo-r3) are configured using the same config file. emerge --info (for non-freezing kernel) Portage 2.0.53_rc5 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.13- gentoo i686) ================================================================= System uname: 2.6.13-gentoo i686 AMD Athlon(tm) XP 2600+ Gentoo Base System version 1.12.0_pre8 ccache version 2.4 [enabled] dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.13 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer -falign-functions=64 -ff ast-math -fprefetch-loop-arrays -ftracer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share /config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/shar e/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer -falign-functions=64 - ffast-math -fprefetch-loop-arrays -ftracer -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict"
some detail that i missed is that i'm using nvidia drivers 1.0.7676, but gentoo-sources-2.6.13-r4 works fine until now. no freeze after 1 hour.
(In reply to comment #1) > some detail that i missed is that i'm using nvidia drivers 1.0.7676, but > gentoo-sources-2.6.13-r4 works fine until now. no freeze after 1 hour. Bad luck. I rebooted and after 20 minutes the system freezed again.
(In reply to comment #0) > The system doesn't freeze if gentoo-sources is used (or vanilla 2.6.13). > It happends after 5-10-15 minutes or even more after boot, under normal desktop By this, you mean that gentoo-sources-2.6.13 does not freeze, but 2.6.13-r2, 2.6.13-r3, 2.6.13-r4 *do* freeze?
(In reply to comment #3) > > By this, you mean that gentoo-sources-2.6.13 does not freeze, but 2.6.13-r2, > 2.6.13-r3, 2.6.13-r4 *do* freeze? Yes. gentoo-sources-2.6.13 does not freeze, but 2.6.13-r2,-r3, -r4 freeze. I don't know about -r1. I've tried different memory modules and no change. I believe that memory isn't a cause. (it should freeze under 2.6.13 too, if there is a memory leak. Or perhaps not? !?) In the next days I'll try to catch a oops using a remote syslog or alt+sysrq procedure.
There is no oops probably as i've incorrectly assumed. It must be a serious panic/freeze, and i don't stand a chance to catch something with a remote syslog. message buffer ->kernel->klogd->syslogd->network stack->wire it's a long path and i've confirmed that there is no network in that freeze state. BUT, with (In reply to comment #4) > (In reply to comment #3) > > > > By this, you mean that gentoo-sources-2.6.13 does not freeze, but 2.6.13-r2, > > 2.6.13-r3, 2.6.13-r4 *do* freeze? > > Yes. gentoo-sources-2.6.13 does not freeze, but 2.6.13-r2,-r3, -r4 freeze. I > don't know about -r1. > I've tried different memory modules and no change. I believe that memory isn't a > cause. (it should freeze under 2.6.13 too, if there is a memory leak. Or perhaps > not? !?) > In the next days I'll try to catch a oops using a remote syslog or alt+sysrq > procedure. There is no oops probably as i've incorrectly assumed. It must be a serious panic/freeze, and i don't stand a chance to catch something with a remote syslog. message buffer ->kernel->klogd->syslogd->network stack->wire it's a long path and i've confirmed that there is no network in that freeze state. BUT, without nvidia drivers there is NO freeze irrespective if i'm using 2.6.13 or the problem versions -r2,r3,r4.
newer versions of nvidia-kernel have been proving problematic for me also but only on a specific card (budget FX). this isnt directly kernel related. Have you tried older nvidia-kernel releases? (and corresponding glx)
Sounds like an nvidia driver bug.
(In reply to comment #7) > Sounds like an nvidia driver bug. Yes, but it's odd that gentoo-sources-2.6.13 isn't affected and the system freezes only when i'm using 2.6.13-r{2,3,4}. I haven't tried older versions of nvidia drivers.
Using gentoo-sources-2.6.14 with the latest nvidia-kernel (1.0.7676-r1) the system does not freeze. So, from my point of view the bug can be closed, 2.6.13-rX is history now for me.
