http://bugzilla.novell.com/show_bug.cgi?id=584554
http://bugzilla.novell.com/show_bug.cgi?id=584554#c9
Jan Beulich changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P2 - High
Status|NEW |NEEDINFO
CC| |pmillett@novell.com
Info Provider| |samuel.kvasnica@ims.co.at
--- Comment #9 from Jan Beulich 2010-03-19 08:31:55 UTC ---
This last post of yours indicates nothing more than possibly broken accounting.
I'll see whether I can observe something similar, but certainly I haven't seen
2.6.33 misbehaviors like the one you describe on any of my test systems. Hence,
without you obtaining detail on what the CPUs actually do when you observe
these lockups (and btw. I'm not even clear whether on .33 you are observing
lockups at all) there's pretty little we can do I'm afraid (unless this can be
reproduced in our lab - Preston?).
Also, just to not confuse things - let's please separate the 11.2 and Factory
issues: Time handling (as noted by you in #3) is now sufficiently different in
those two kernels, and hence unless proven otherwise I have to assume that the
similar symptoms (if so in the first place) are caused by different problems.
Consequently, please open a new bug for the Factory kernel problems
(transferring all relevant information from here), and we'll continue looking
at the 2.6.31 issue here.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.