https://bugzilla.novell.com/show_bug.cgi?id=486554 Summary: Kernel 2.6.27.19-3.2 Unable to access machine after a day or so, but all VMs continue to function normally Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bdarlt@gmail.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009020414 CentOS/3.0.6-1.el5.centos Firefox/3.0.6 I recently installed OpenSuSe 11.1 to run a few VMs we had running on an OpenSuSe 10.2 machine. I started all the VMs on the 11.1 one machine, and all seemed well. A few days later I tried to access the machine (Dom0) and ssh just hung. So I tried the serial console, and logged in and got a shell. The first thing I ran hung the serial console, and nothing would unhang it. I attempted sysrq, but I am not sure if that was enabled, or if my iLO2 was passing it along. I found Bug 463372 - Kernel 2.6.27.7 SuSE file monitoring serious bug (inotify) , which sounds very similar what I am experiencing. Except I am not running Samba or Dovecot. But I am running the xen kernel. All VMs on the machine behaved the way they should during the week that I couldn't access their Dom0 (I had to wait for a scheduled time to move VMs and reboot the Dom0). I am happy to debug and try things, but am unsure how to recreate the hang. All system logs just stopped, so I couldn't see anything out of the ordinary. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Expected Results: The machine should have remained accessible. We have 2 Dual-Core AMD Opteron(tm) Processor 2216 HE The machine (Dom0) in question is a blade, HP ProLiant BL465c G1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.