Bugzilla – Bug 396200
kernel freeze
Last modified: 2008-07-07 17:47:40 UTC
After working some minutes in KDE-3.5.9 I always get a kernel freeze. This only occurs with kernel-2.6.25.4-8-pae and kernel-2.6.25.4-8-default never with kernel-2.6.25.4-8-vanilla. I've a nvidia-card in my system, the freeze occurs with both drivers, nvidia and nv.
*** Bug 396238 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 392198 ***
I don't have the system freeze at boot-time. The system freezes minutes or sometimes hours later. The freeze never occurs with the vanilla-kernel. I've tried it on an athlon dualcore and a Celeron M notebook. On both sytems and with with both kernels (default and pae) the freeze occurs. The filesystem is reiserfs on both. Maybe it has something to do with the additional reiser patches.
We are really going to need some kind of oops report here in order to be able to track this down better. I'm going to lower the severity as it seems you are the only one having this problem.
I also have the freeze in the new kernel-2.6.25.5-1.1-pae. I found a lot of the following lines in /var/log/messages: kernel: REISERFS warning (device md0): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) associated with [274347 324123 0x0 SD] The freeze seems to be related with using reiserfs.
I can confirm that. One more clue to the problem is, that since I installed OpenSuSE 11 on another partition with ext3, no more freezes occured.
Me too. X86-64 system, updated to OpenSUSE 11 from 10.3, ReiserFS. I see kernel freezes within a few minutes after logging into KDE 3.59 or 4.0.82 using the default kernel. It does not make a difference if I use the nv or the nvidia driver. Freezes seem to occur mostly, perhaps always, when using the mouse. I saw no freeze in the idle kdm screen for hours. Now I'm running the vanilla kernel. Works just fine.
I have same problem. ReiserFS. I remembered that, kernel saboteurs are sabotaging ReiserFS4. Are they start to sabotaging ReiserFS3 in distros? I don't understand that why they are doing this. It's the best FS out there. Is this bug here for force users to another file system? If it's true, it's similar pattern that in windows FAT32 32GB limit partition size. And its also interesting thing that releasing a Gold Master version with critical bug like that. Using vanilla is better I think.
Please don't adjust knobs on bug reports that aren't yours. The priority field is only to be set by NTS, and the platform isn't a checklist. I'll change it to "all."
*** This bug has been marked as a duplicate of bug 389656 ***