When will 2.6.27.10 leave factory and be available as an update?
> I don’t know, but I have it too with our good server locking up around
> once a day around 17:00h each day…
my opinion is that almost all locks which occur at a particular time
each day is a setup problem somewhere within the system…
have you checked what crons start daily at 17?
try installing atop and running it with a snapshot look every 10
seconds from (say) 16:59:00 to 17:01:00 and see if you can’t “catch”
what is starting, and locking your system…
For me, the factory kernel 2.6.27.10 led to a stable system.
It was really easy to install:
- YaST->Repositories: Add html: http://download.opensuse.org/factory/repo/oss/
- YaST->Install Software->search: kernel -> select kernel-2.6.27-10
- Yast->Boot: surprise->the new kernal was added as an alternate boot kernel to the GRUB configuration
- Reboot -> thant’s all
Thanks to all!
Harald
I was also having this problem and the updated kernel has corrected the problem. I was really close to move back to 11.0 because this issue was sooooo annoying.
Well, belay my last. I thought it was working alright but more freezes. I did notice I could SSH into my machine so I am wondering if the Gnome window manager is freezing. Anyways, I have been annoyed long enough, moving back to 11.0 it appeared to be more stable. I was running 11.1 with all the current updates and patches with 3GB RAM on a dual-core processor. All my hardware checks out, I ran diags on everything. Something with openSUSE 11.1.
If you can ssh into your machine, it’s probably a different problem. The symptom of this inotify bug is that nothing is active, not even the screen can be made to wake up by typing at the keyboard. The only thing that seems to work is ping reply.
If you are not running samba or dovecot, that also points to a different problem. Maybe graphics card related.
I have this problem too. I tried to update kernel enabling factory repo, but got problems with nvidia drivers:
YaST2 conflicts list - generated 2009-01-27 21:23:29
nvidia-gfxG02-kmp-pae-180.22_2.6.27.7_9.1-4.1.i586 requires kernel(pae:drivers_i2c) = df4119f043cf19b3, but this requirement cannot be provided
] do not install kernel-pae-2.6.27.10-2.5.i586
] deinstallation of nvidia-gfxG02-kmp-pae-180.22_2.6.27.7_9.1-4.1.i586
] Ignore some dependencies of nvidia-gfxG02-kmp-pae
YaST2 conflicts list END
I tried to ignore depedencies, but x didn’t start after kernel update. I had to go back to 2.6.27.7.
How should this be handled? Should I remove nvidia drivers, update kernel and install drivers after that?
openSUSE 11.1 64bit
ECS GeForce6100SM-M / AMD64X2 5600 / 1gb ram / 200gb sata / 250gb ide / dvd+rw / Wintv pvr 150 / kde 3.5 / default kernel 2.6.27.7
I’ve been having random system hang/crashes for a while now. It happens in either console or X. I will be working on something and the screen scrambles and the system locks forcing a manual reboot. It has recently started to do this when I try to rip my cd’s to ogg, in dmesg there will be an IO error from /dev/sr0 then crash. It happens VERY quickly when I try to play a DVD or rip it. Almost as if it has something to do with the nVidia part of the system. I’ve tried asking about different things I’ve seen in the log files but most are dismissed as nothing to worry about.
I have no idea what the problem is, but it got worse when I went from 11 to 11.1. Today alone I’ve had to reboot 5+ times… I got mad and lost track after that but I’m sure its more than 7. I haven’t had a stable install going in almost 3 months now and its really bugging me… not enough to go back to windows though 
When the system hangs, there seems to be no information written to the logs about whats happening. Is there some package I can install to assist this? If anyone knows what log files to look in for anything that would help figure this out, please let me know.
Thanks folks
I don’t think this particular bug is the problem you’re having. It is new in 11.1 and only affects people running servers with Samba or dovecot. Better start a new thread.
Didn’t consider that I might be running samba? I am.
Nice that you are so smart to know for sure that this is not the bug I’m having (waving his hand in a jedi mind trick manner)…
Seems none of the places I’ve posted a question have anything to do with the problems I’m having. Wonder why that is.
Did you actually read my post? There was enough info that even if this is not the bug I’m having (wave) you could possibly point me in a direction where I might get some kind of help. Maybe?
dcdugger, we all have frustrations with our problems. Please, lets try to keep this on the level. Also, your post time is almost the same as ken_yaps. He could be replying to user m_kane and may not have even seen your post. How about giving him the benefit of the doubt.
In addition, this problem thread was started by ken_yap, and eventually he identified a solution to solve his specific problem. He provided the solution in this thread.
If you applied the solution he applied (which is WELL documented in this thread) and it does not work, then you most likely DO have a different problem.
Ken_yap is trying to help you, by suggesting you start a new thread. He is NOT trying to brush you off.
Note please, we are almost all volunteers here. We don’t get paid for this. Hence the recommendations we give are typically in a best effort basis to help. Its made with good intent, with no compensation.
I believe ken_yap’s recommendation (to start a new thread) is likely to get you the best support possible.
Good luck and best wishes.
I did read your post. Based on your description that it also happened to you in 11.0 I am pretty sure that this is not the bug you are looking for. This bug is specific to 11.1 and is a kernel bug that affects only certain versions.
However if you really believe that this is your bug, then look at one of my previous posts (pot calling the kettle black over not reading the thread) and you will see how you can update your kernel to the factory version where the inotify bug is fixed.
I have the same problem on Kubuntu 8.10 with KDE 4.1 and kernel …9.
I have the same exact problem with my Compaq CQ60 Laptop. System locks up randomly. Lat time it locked up in a ftp session as soon as I tried “!ls”
Latest update of kernel to 2.6.27.19-3.2 from update repo has been running on my machine for over 24 hours just fine so finally the fix has made its way out of Factory. Case closed as far as I’m concerned.
I’m running into this issue as well. I’ve got a clean install, I just did a standard KDE installation with no changes to the default packages. My system freezes without fail any time I try to install packages through the yast software manager. Sometimes I can get as far as actually starting the download for new packages, other times I can just be browsing the list. I can do system updates just fine, just no new stuff. It also freezes randomly without trying to install anything. It froze earlier tonight, I logged in, started firefox, went to a site that needed flash and it asked me to install, clicked manual install, the window for Adobe’s site popped up and the system froze (before the site loaded). XP 64 runs without any trouble, as does the express gate os that’s on the motherboard. KDE itself is also very sluggish, but I assume that’s partly because of the older video card I’m running right now and no video drivers yet.
System specs:
Intel Core i7 965
6Gb ram
Asus p6t deluxe v2 mobo
OpenSuse 11.1 x64
ATI Radeon 9250 (will be replaced by a Nvidia gtx 295 next week)
I don’t think this bug is your problem then. The freeze described doesn’t happen until those affected network services (dovecot, samba) are run which can be minutes or hours down the track. I would start a new thread if I were you otherwise your query might get lost.
Ok, thanks for the quick response.
I having excatly this same problem. I’ve updated the kernel, uninstalled samba, made sure that beagle isn’t running, and my system still continues to lock up. I was wondering do you think that removing dovecot and replacing it with courier mail may resolve this problem?
If you upgraded the kernel to 2.6.27.21-0.1.2 and your computer still freezes, it’s a different problem. Definitely. Dovecot and samba work fine once this kernel bug is gone.