It is important that this exported interface remains stable because modules written for a particular kABI would need to be recompiled if the interface does change in a subsequent kernel version. Thanks, Chris Lalancette Comment 114 Alok Kataria 2009-01-26 21:06:09 EST (In reply to comment #113) > I've uploaded a test kernel that contains this fix (along with several others) > to Comment 30 Rik van Riel 2008-10-08 12:03:50 EDT *** ERROR - ABI BREAKAGE WAS DETECTED *** The following symbols have been changed (this will cause an ABI breakage): cpu_data boot_cpu_data The The "Disable softlockup" patch replaces "fix 64bit softlockup warnings" patch.
Instructions To Fix (Error - Abi Breakage Was Detected) error you need to follow the steps below: Step 1: Download (Error - Abi Breakage Was Detected) Repair Tool How are these checksums generated? The time does still hold tight but the support teams will be questioning this when they see it in production. Patch series vm_tsc_calibration.patch minimal-clocksource-for-64bit.patch fix-lockup-warnings-for64bit.patch Please have a look at these patches.
Update '/home/GIT/RHEL7.2/rhel7/localversion' to change. Comment 44 Glauber Costa 2008-10-16 08:42:20 EDT From reading the code only, the patches seem fine to me as far as KVM is concerned. Rik also promised to re-review the updated patches at some point, so that will be another pair of eyes on it. Instead, I went with the upstream solution (namely git hash > 3da757daf86e498872855f0b5e101f763ba79499), and use the "lpj_fine" variable to > basically do the same.
Makes sense. > > 6) Patch 5 (Disable softlockup with the TSC based algorithm under VMware) is > another one-off for RHEL-5. How reproducible: # cat /proc/self/sched Actual results: cat (30286, #threads: 1) ------------------------------------------------------------------- se.exec_start : 33010432583.086650 se.vruntime : 18693974.064711 se.sum_exec_runtime : 3.290863 nr_switches : 2 nr_voluntary_switches : 1 nr_involuntary_switches : 1 se.load.weight Comment 14 Alok Kataria 2008-09-25 17:37:36 EDT Hi Rik, I have attached all the patches. Reload to refresh your session.
vmware tsc calibration, but more generic to accomodate other hypervisors https://bugzilla.redhat.com/attachment.cgi?id=320098 4. Comment 17 Rik van Riel 2008-09-25 19:48:30 EDT I understand that you would like to see the patches in RHEL 5.3, however it is very late in the development cycle to Without this patch we have a bug where we update the jiffies value too fast with divider=. Why doesn't the upstream kernel need to do this?
This code is used by the vendor to identify the error caused. Novice Computer User Solution (completely automated): 1) Download (Error - Abi Breakage Was Detected) repair utility. 2) Install program and click Scan button. 3) Click the Fix Errors button when scan Note that this is a unusual case and should only happen under extreme CPU load or some types of I/O load; in either case it does not indicate a real bug My apologies.
Error - Abi Breakage Was Detected Error Codes are caused in one way or another by misconfigured system files in your windows operating system. https://www.ibm.com/developerworks/forums/thread.jspa?threadID=355717 I can compile with the flag --without kabichk, but I don'tknow if really is that the solution or not.The package build stops at this point:+ echo '**** kABI checking is enabled Comment 7 Alok Kataria 2008-09-24 22:50:14 EDT (In reply to comment #6) > Backporting dmi_name_in_vendors seems perfectly safe. This isn't setup in the upstream kernel, but is > > in this patchset.
After the RHEL 5.3 sprint is over, upstream discussions should have settled down and I'll check these patches for kABI impact (looks like there should be no major problem). Ah, OK. Last modified: 2011-11-03 13:33:26 EDT. That seems relatively > > uncontroversial. > > Okay. > > > > > 2) For the second patch (code to detect running on vmware and get tsc > > frequency
The Error - Abi Breakage Was Detected error may be caused by windows system files damage. Once permission to include this feature in RHEL 5.4 has been granted I will submit these patches for review internally. The current patches I'm looking at are available at > http://new-people.redhat.com/clalance/bz463573 (compile tested only at the > moment), but I do have some questions and comments about why we are diverging Please note this was done only for the 64bit change for RHEL, with the clocksource implementation in mainline this is mostly taken care of by the schedclock, but ya there are
Now whenever such changes happen for any symbol, the checksum corresponding to that symbol also change which leads to easy detection of kernel ABI change (or breakage). Topic Forum Directory > dW > Eserver > Forum: IBM BladeCenter Forum > Topic: Linux Qlogic driver update on HS22 problem 2 replies Latest Post - 2011-01-04T18:35:33Z by Novikov_Alexander Display:ConversationsBy Date Comment 38 Alok Kataria 2008-10-11 23:01:53 EDT (In reply to comment #36) > Created an attachment (id=320098) [details] > vmware tsc calibration, but more generic to accomodate other hypervisors > >
Comment 72 Rik van Riel 2008-12-04 14:14:08 EST Created attachment 325724 [details] add serial key for dmi check Comment 73 Rik van Riel 2008-12-04 14:16:44 EST Created attachment 325725 [details] code However, as the testing has demonstrated, that comment #75 patch was not successful in preventing the warnings in all cases. Thanks, Alok Comment 15 Rik van Riel 2008-09-25 18:03:58 EDT These patches look reasonable to me. Comment 47 Alok Kataria 2008-10-16 15:20:41 EDT (In reply to comment #46) > The only question remaining is, what is happening with this code upstream? > > Is anybody submitting it
Especially when they start out with a line saying "BUG: soft lockup - CPU#0 stuck ...". I have requested product management to consider this for inclusion in RHEL 5.4. basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.) Recommended Solution Links: (1) Chris Lalancette Comment 118 Chris Lalancette 2009-02-11 04:02:59 EST OK, I've done a thorough look through of the patches.
Why is this? Chris Lalancette Comment 121 Alok Kataria 2009-02-12 16:54:16 EST (In reply to comment #120) > Again, thanks for taking the time with this; hopefully we won't have to go > through VM on VMware ESX Server 3.5.0 build 84374 - 32-bit or 64-bit? 64-bit - What processor? If you mean the functionality to detect whether we are running on VMware, yes i plan to push patches for this upstream but that is going to be a lenghty process
However, there are parts here that differ from upstream. Another point is that we wanted to keep changes to a distro kernel as minimal as we could, doing a generic hypervisor level interface resulted in lot of code addition, but If the messages are innocuous, they shouldn't be appearing on the console at all. Each of four VMs were running precisely: while true; do dd if=/dev/zero of=/tmp/bigfile bs=4096k count=100>/dev/null 2>&1; done - What's the frequency?
It can happen when the hypervisor is under high load, and does not schedule the VM often enough. BMW engine error codes(flashes) and their possible causes…. Does > upstream need this? Alok, Chris, please review.
When the kernel is built for Fedora, these exported symbols are stored in a file called Module.symvers. Thank you for the summary. From: Owen Taylor [Thread Prev][Thread Next] [Thread Index] [Author Index] The GNOME Project. The patch in comment #75 attempted to notify the softlockup code when the VM was descheduled by the hypervisor, but I don't think it is fool proof.
The exported binary interface that I keep referring to is nothing except a list of symbols which have been decided to be exported. it's detecting cases where the kernel is not able to reschedule).