MCE errors with kernel 2.6.32.x

I'm running a dual Xeon machine, x86_64, 8G memory, Radeon HD 4350 graphics.
Back in February, I upgraded the system and went from the 2.6.31.6-1 kernel to the 2.6.32.7-1 kernel, at which point the machine started doing random reboots and reporting MCE errors. I posted over in the newbie section but marked it solved when a downgrade to the 2.6.31.6-1 kernel seemed to solve the problem. At that point I did run a memory test and found no errors, and temperature monitoring didn't show any problems.
The machine has been rock solid ever since.
Last night I upgraded everything again, and this time went to the 2.6.32.10-1 kernel. The random reboots began again, again with MCE errors. Although I've only caught one of them and didn't get things written down, it did look like different error messages.
I've now been working on it for a couple hours with no stability problems. Before downgrading, I was getting random reboots every 15 minutes or so. Other than the kernel downgrade, I haven't changed anything.
I haven't been able to find anything out about the problem, and other than preventing kernel upgrades for awhile, am not sure how to proceed.

Regarding link quality: I had found complaints from other users (on Ubuntu boards) that the open source Atheros drivers for linux have a problem where they didn't actually utilize the wifi's full broadcast/receive power.
This leads to low link quality even when you are very close to the access point. The random connection drops happen because your card doesn't hear the AP's beacon clearly enough, and it thinks you've moved out of range of the network.
The advice given was to use ndiswrapper to install the (proprietary) wifi Windows driver for your card (which in my case I was able to download from Atheros' web site). This boosts the card's power to full, giving you better link quality.
In my case signal level and link quality improved by about 20-30 dBm and 20% respectively. The connection dropouts stopped altogether.
I've heard mention on some other threads here that the latest ath-drivers in the linux 2.26.32 kernel are improved, so the problem may not be as bad as before. I have not tried them though, since the ndiswrapper solution is working well for me.

Similar Messages

OAS 4.0.8.1 on Linux: Error with Kernel 2.2.18

Hi,
on our linux-box OAS 4.0.8.1 is running under Kernel 2.2.13 (SMP, SuSe 6.3) without big problems.
Today we have tried to run OAS under Kernel 2.2.18 (the latest stable from the 2.2.x series) but the OAS reports an error while starting a listener (something with ORB error).
Is anybody running OAS under 2.2.18?
Any suggestions?
Bye
Halil
null

Originally posted by larsonm1:
After installing patch for Backport bug # 1227322, I still have the same problem with
'owsctl start' hanging sometimes (about 30% of the time). It usually waits after it
says, "waiting for ORB to be ready...", and I have no error messages in any of the
log files.
Configuration:
Dell PowerEdge 6300 Quad-CPU
512 MB memory
OAS4.0.8.1 w/ patch upto 1227322
Linux 6.1
glibc 2.2
I get this when executing either from the node manager (graphically) or at the command line.
Any Ideas?
Friends.
I am with the same problem.
Gediel.

[SOLVED] VMware player update error with kernel 2.6.35

I have WMware player 3.1, it was working fine until I upgrade to kernel 2.6.35. Here is WMware error message:
aoû 24 20:51:34.275: app-3076503232| Log for VMware Workstation pid=6643 version=7.1.0 build=build-261024 option=Release
aoû 24 20:51:34.275: app-3076503232| The process is 32-bit.
aoû 24 20:51:34.275: app-3076503232| Host codepage=UTF-8 encoding=UTF-8
aoû 24 20:51:34.275: app-3076503232| Logging to /tmp/vmware-root/setup-6643.log
aoû 24 20:51:34.377: app-3076503232| modconf query interface initialized
aoû 24 20:51:34.378: app-3076503232| modconf library initialized
aoû 24 20:51:34.468: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.477: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.509: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.553: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.585: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.695: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.700: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.705: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.710: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.714: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.779: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.783: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.788: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.793: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.797: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.803: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.837: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.948: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.953: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.958: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.962: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.967: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.973: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:35.013: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:35.187: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.192: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.198: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.203: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.208: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.656: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.657: app-3076503232| Building module vmmon.
aoû 24 20:51:35.657: app-3076503232| Extracting the sources of the vmmon module.
aoû 24 20:51:35.697: app-3076503232| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.35-ARCH/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.5.1
aoû 24 20:51:41.031: app-3076503232| Failed to compile module vmmon!
Thanks for help!
Last edited by srivo (2010-10-26 02:05:16)

I tried this it didn't work:
% wget http://www.sputnick-area.net/scripts/vm … .6.35.bash
--2011-06-15 11:18:03-- http://www.sputnick-area.net/scripts/vm … .6.35.bash
Resolving www.sputnick-area.net... 91.121.18.134
Connecting to www.sputnick-area.net|91.121.18.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6992 (6.8K) [text/plain]
Saving to: “vmware7.1.1-patch-kernel-2.6.35.bash.1”
100%[======================================================================>] 6,992 --.-K/s in 0.07s
2011-06-15 11:18:06 (97.8 KB/s) - “vmware7.1.1-patch-kernel-2.6.35.bash.1” saved [6992/6992]
% ./vmware7.1.1-patch-kernel-2.6.35.bash
This script have been already applied !
% vmware-modconfig --console --install-all
Stopping vmware (via systemctl): [ OK ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root-62598440/modules/vmmon-only'
make -C /lib/modules/2.6.38.7-30.fc15.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.38.7-30.fc15.x86_64'
CC [M] /tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.o
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c: In function ‘init_module’:
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c:425:15: error: ‘struct file_operations’ has no member named ‘ioctl’
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c:1736:7: error: implicit declaration of function ‘kernel_locked’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-root-62598440/modules/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.38.7-30.fc15.x86_64'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-root-62598440/modules/vmmon-only'
Unable to install vmmon

Kernel broken. Pacman errors with PGP sig [solved]

I had the unlucky situation to have a power failure in the middle of a Kernel upgrade using Pacman. System came back up and the kernel was not installed. So I have NO working OS on the machine.
I can boot into a live USB environment and chroot into my install. I can run Pacman, and thought I could just pacman -S linux and let it do it's thing and I'd be all good. but... I get package signature PGP verification error message and cannot install anything with Pacman.
Of course, the error with the Kernel install happened before Daylight savings time, and now we're INTO DST, so I suspect it's a "time" issue as reported on the Wiki.
timedatectl will not work in the chroot environment. Can't connect to dbus. I am totally migrated to a systemd install, but systemctl enable dbus.service does not start the dbus from within the chroot environment.So I cannot even see if my chroot environment is on the right time. 'cal' works and shows the proper date, which I can change in the BIOS to whatever I want.
running ntpd first doesn't fix the error with Pacman.
Any ideas?
Last edited by hooya (2013-03-16 20:02:35)

I tried that and didn't work either, because there were files left behind in the initial installation that was broken. Even after removing them I got disk spacer errors (there was no disk space issue, so that's weird).
I did get it finally though. I ended up using the initial pacstrap install script to install the base packages as per the Beginner Install Guide (and selected only option 26 "Linux") which did work, probably because it was operating from outside of the chroot environment. A bit "hacky" but I'm at least typing this message from my normal installation this time!

MacBook Pro crashes with kernel errors

Hi, i'm havinge troubles with my 2009. macbook pro. It keeps crashing down with kernel errors.
I took it to apple, payed for a repair and they didn't fix it. Now i don't know what to do. I recently noticed that my right fan isnt working.
I'm leaving you with one of my error reports if you know how to read them.
Btw, hardware test simple and extended one reports ok. Disk warrior also. Could it be the temperature? Last time it crashet it was at about 76 celsius...crashes are not time reliable, sometimes i just turn it on and it crashes while loading os (its not yet hot), sometimes it can work for an hour or two then die again...
Interval Since Last Panic Report: 43496 sec
Panics Since Last Report:          5
Anonymous UUID:                    382F5493-4035-4ECA-A0BC-7F843351D3F6
Wed May 18 20:24:17 2011
panic(cpu 0 caller 0x2aab59): Kernel trap at 0x002aa5ab, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x80813408, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x002aa574, EBX: 0x0000000e, ECX: 0x00010006, EDX: 0x00000002
CR2: 0x80813408, EBP: 0x00813448, ESI: 0x80813580, EDI: 0x00813460
EFL: 0x00010097, EIP: 0x002aa5ab, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000002
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x813198 : 0x21b510 (0x5d9514 0x8131cc 0x223978 0x0)
0x8131e8 : 0x2aab59 (0x59aeec 0x2aa5ab 0xe 0x59b0b6)
0x8132c8 : 0x2a09b8 (0x8132e0 0x0 0x813448 0x2aa5ab)
0x8132d8 : 0x2aa5ab (0xe 0x48 0x10 0x10)
0x813448 : 0x2a09b8 (0x813460 0x0 0x8135c8 0x2aa574)
0x813458 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x8135c8 : 0x2a09b8 (0x8135e0 0x0 0x813748 0x2aa574)
0x8135d8 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x813748 : 0x2a09b8 (0x813760 0x0 0x8138c8 0x2aa574)
0x813758 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x8138c8 : 0x2a09b8 (0x8138e0 0x0 0x813a48 0x2aa574)
0x8138d8 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x813a48 : 0x2a09b8 (0x813a60 0x0 0x813bc8 0x2aa574)
0x813a58 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x813bc8 : 0x2a09b8 (0x813be0 0x0 0x813d48 0x2aa574)
0x813bd8 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x813d48 : 0x2a09b8 (0x813d60 0x0 0x813ec8 0x2aa574)
0x813d58 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x813ec8 : 0x2a09b8 (0x813ee0 0x0 0x814048 0x2aa574)
0x813ed8 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x814048 : 0x2a09b8 (0x814060 0x0 0x8141c8 0x2aa574)
0x814058 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x8141c8 : 0x2a09b8 (0x8141e0 0x0 0x814348 0x2aa574)
0x8141d8 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x814348 : 0x2a09b8 (0x814360 0x0 0x8144c8 0x2aa574)
0x814358 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x8144c8 : 0x2a09b8 (0x8144e0 0x0 0x814648 0x2aa574)
0x8144d8 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x814648 : 0x2a09b8 (0x814660 0x0 0x8147c8 0x2aa574)
0x814658 : 0x2aa574 (0xe 0x48 0x10 0x10)
0x8147c8 : 0x2a09b8 (0x8147e0 0x0 0x814948 0x2aa574)
0x8147d8 : 0x2aa574 (0xe 0x48 0x10 0x10)
    Backtrace continues...
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10J869
Kernel version:
Darwin Kernel Version 10.7.0: Sat Jan 29 15:17:16 PST 2011; root:xnu-1504.9.37~1/RELEASE_I386
System model name: MacBookPro5,4 (Mac-F22587A1)
System uptime in nanoseconds: 6413575130
unloaded kexts:
(none)
loaded kexts:
com.apple.driver.AppleUSBTCButtons    200.3.2 - last loaded 1848219394
com.apple.driver.AppleUSBTCKeyEventDriver    200.3.2
com.apple.driver.AppleUSBTCKeyboard    200.3.2
com.apple.driver.AppleIRController    303.8
com.apple.iokit.SCSITaskUserClient    2.6.5
com.apple.driver.AppleUSBCardReader    2.5.8
com.apple.BootCache    31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
com.apple.iokit.IOAHCIBlockStorage    1.6.3
com.apple.driver.AirPortBrcm43xx    423.91.27
com.apple.driver.AirPortBrcm43224    427.36.9
com.apple.driver.AppleAHCIPort    2.1.5
com.apple.driver.AppleFWOHCI    4.7.1
com.apple.nvenet    2.0.15
com.apple.driver.AppleUSBHub    4.1.7
com.apple.driver.AppleUSBEHCI    4.1.8
com.apple.driver.AppleUSBOHCI    4.1.5
com.apple.driver.AppleSmartBatteryManager    160.0.0
com.apple.driver.AppleEFINVRAM    1.4.0
com.apple.driver.AppleRTC    1.3.1
com.apple.driver.AppleHPET    1.5
com.apple.driver.AppleACPIButtons    1.3.5
com.apple.driver.AppleSMBIOS    1.6
com.apple.driver.AppleACPIEC    1.3.5
com.apple.driver.AppleAPIC    1.4
com.apple.driver.AppleIntelCPUPowerManagementClient    105.13.0
com.apple.security.sandbox    1
com.apple.security.quarantine    0
com.apple.nke.applicationfirewall    2.1.11
com.apple.driver.AppleIntelCPUPowerManagement    105.13.0
com.apple.driver.BroadcomUSBBluetoothHCIController    2.4.0f1
com.apple.driver.AppleUSBBluetoothHCIController    2.4.0f1
com.apple.iokit.IOBluetoothFamily    2.4.0f1
com.apple.driver.AppleUSBMultitouch    206.6
com.apple.iokit.IOUSBHIDDriver    4.1.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice    2.6.5
com.apple.iokit.IOBDStorageFamily    1.6
com.apple.iokit.IODVDStorageFamily    1.6
com.apple.iokit.IOCDStorageFamily    1.6
com.apple.iokit.IOSCSIBlockCommandsDevice    2.6.5
com.apple.iokit.IOUSBMassStorageClass    2.6.5
com.apple.driver.AppleUSBMergeNub    4.1.8
com.apple.driver.AppleUSBComposite    3.9.0
com.apple.driver.XsanFilter    402.1
com.apple.driver.AppleFileSystemDriver    2.0
com.apple.iokit.IOAHCISerialATAPI    1.2.5
com.apple.iokit.IOSCSIArchitectureModelFamily    2.6.5
com.apple.iokit.IO80211Family    314.1.1
com.apple.iokit.IOAHCIFamily    2.0.4
com.apple.iokit.IOFireWireFamily    4.2.6
com.apple.iokit.IONetworkingFamily    1.10
com.apple.iokit.IOUSBUserClient    4.1.5
com.apple.iokit.IOUSBFamily    4.1.8
com.apple.driver.NVSMU    2.2.7
com.apple.driver.AppleEFIRuntime    1.4.0
com.apple.iokit.IOHIDFamily    1.6.5
com.apple.iokit.IOSMBusFamily    1.1
com.apple.kext.AppleMatch    1.0.0d1
com.apple.security.TMSafetyNet    6
com.apple.driver.DiskImages    289
com.apple.iokit.IOStorageFamily    1.6.2
com.apple.driver.AppleACPIPlatform    1.3.5
com.apple.iokit.IOPCIFamily    2.6
com.apple.iokit.IOACPIFamily    1.3.0
Model: MacBookPro5,4, BootROM MBP53.00AC.B03, 2 processors, Intel Core 2 Duo, 2.53 GHz, 4 GB, SMC 1.49f2
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.131.36.9)
Bluetooth: Version 2.4.0f1, 2 service, 12 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS545025B9SA02, 232.89 GB
Serial ATA Device: MATSHITADVD-R   UJ-868
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24400000
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0x26500000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0237, 0x04600000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x04500000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8213, 0x06110000

If it's overheating then that's the thermal cut out protecting the system - don't you hear the fan's going at maximum ? Are you using it on a flat hard surface so there's room for air to circulate ?
If you can't hear the fans running fast then I suggest you run the hardware tests from your install DVD (insert and reboot holding down d) to see if it shows any SNS (sensor) or MTR (fan motor) errors, if so get it to Apple for a fix.

Pls assist in Error " OS not Supported with Kernel"

Hello
I am new to SAP. I did a fresh Install of ERP 6.0 on Windows 2008 R2 64bit SP1. The installation went fine but when connecting using SAP GUI I am getting an error. Please see below. Looks like some Kernel upgrade issue. Please assist in what needs to be done. The Error and Kernel Info is listed below.
Error
[http://i905.photobucket.com/albums/ac258/amirsd1/Error.jpg]
Current Kernel Info
http://i905.photobucket.com/albums/ac258/amirsd1/kernel.jpg
Any tips or suggestion would be really appreciated.
Edited by: amirsd on Jul 6, 2011 10:21 PM

Hi,
As per you screens, it look like you have EHP4 installed on your system. And DVD's of EHP4 that contains kernel are quite old which is not complied for NT version 6.1. So please do the kernel upgrade with latest kernel available then your will be resolved.
Thanks
Sunny

Error 41 - Kernel Power in event log after clean shutdown - Windows 8.0

HP Envy H9-1405A - 16MB RAM, Windows 8.0, and up to date with updates. (16 months old but under extended h/w warranty). All user data backed-up daily.
After problems earlier today I noticed that after a controlled shutdown and start from cool (ie on/off button on PC, not mains power at the wall) the startup took over 10 minutes. Event browser showed error 41 - Kernel Power - "after system crash or lost power unexpectedly", which it definitely hadn't as I was testing a controlled shutdown.
When starting from overnight sleep mode this morning it came up with blue screen and an error mssage something like 'hard disk driver error', or similar (before first coffee so I wasn't really awake). PC wouldn't restart in anything like reasonable time until powered off at wall, after which it struggled up and ran normally for a while. Went out for a couple of hours and on return again the PC wouldn't re-start from sleep mode. Again used the wall power switch to effect the restart and PC and after very slow restart it ran normally. Event log showed Startup Repair ran due to a corrupted registry hive, and reboot used an earlier version.
Checkdisk ran clean and the HP Support Assistant diags just looped for ever.
I then tried a system restart, which worked but took a long time, and then a controlled power down and start from cool which also took a long time as described above. I've temporarily turned off sleep mode so as to keep working.
Question - do I have a transient software problem which might be fixable with Recovery, or failing hardware that should be covered by warranty, and where might I find some hardware diagnostics to show to the supplier? Thanks.

Hello @mikerb,
I have read your post on how your desktop computer is displaying an error message in regards to a Kernel event log, and I would be happy to assist you in this matter!
To further diagnose this issue, I recommend following the steps in this document on Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first". This should help to resolve the critical error message.
Just to be on the safe side, I also suggest following this resource on Testing for Hardware Failures (Windows 8); which should help determine if there is a hardware defect with one or multiple hardware components on your computer.
Please re-post with the results of your troubleshooting, and I look forward to your reply!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

Oracle 10g on SuSE 9 with kernel 2.6.4

Hi,
i have installed Oracle 10g on SuSE 9 Professional with kernel 2.4.21-192 and it works fine.
For testing purposes i have installed a 2.6.4 Kernel and get the following error on database startup:
SQL> Connected to an idle instance
SQL> ORA-27125: unable to create shared memory segment
Linux Error: 1: Operation not permitted
SQL> Disconnected
Do you have any hints or is the kernel 2.6 not supported.
Thanks Klaus

/* using strace I have narrowed this down to the shmget call for allocating SGA memory. Specifically 2.6 kernel generates a WAIT in this call and Oracle specify IPC_NOWAIT flag, hence the failure condition.*/
#include <sys/types.h>
#include <sys/shm.h>
#include <sys/types.h>
#include <sys/mman.h>
#include <errno.h>
extern int errno;
#define SHM_HUGETLB 04000
#define SGA_SIZE 192937984
#define dprintf(x) printf(x)
#define ADDR 3285588844UL
main()
int shmid;
int i, j, k;
volatile char *shmaddr;
if ((shmid = shmget(ADDR, SGA_SIZE, IPC_CREAT|IPC_NOWAIT|IPC_EXCL|0660) )
< 0) {
perror("IPC_NOWAIT Failure:\nTry without NOWAIT condition");
if ((shmid = shmget(ADDR, SGA_SIZE, IPC_CREAT|IPC_EXCL|0660) )
< 0) {
perror("Failure:");
exit(1);
printf("shmid: 0x%x\n", shmid);
shmaddr = shmat(shmid, (void *)ADDR, SHM_RND) ;
if (errno != 0) {
perror("Shared Memory Attach Failure:");
exit(2);
printf("shmaddr: %p\n", shmaddr);
dprintf("Starting the writes:\n");
for (i=0;i<SGA_SIZE;i++) {
shmaddr[i] = (char) (i);
if (!(i%(1024*1024))) dprintf(".");
dprintf("\n");
dprintf("Starting the Check...");
for (i=0; i<SGA_SIZE;i++)
if (shmaddr[i] != (char)i)
printf("\nIndex %d mismatched.");
dprintf("Done.\n");
if (shmdt((const void *)shmaddr) != 0) {
perror("Detached Failure:");
exit (3);

[SOLVED] errors with fdisk and cryptsetup; is my drive going bad?

I'm having issues with re-formatting an external hard drive using dm-crypt. It was previously formatted with TrueCrypt/NTFS, which I used as a shared backup drive between Windows and Arch. At some point, it stopped being able to mount, which I attributed to allowing Windows to "fix" it after improper dismount (e.g. a hard kill).
I decided to re-format with ext4 and only use it from Arch, but now I'm wondering if I may have a hardware issue with the drive. I've tried a lot more (like going through the full zero write after mounting the drive as a temporary dm-crypt device), but here's the condensed version to illustrate the problem.
system info
This is on a fresh boot. Just adding that as I've had issues with kernel modules after updating if a new kernel comes through. A fresh boot removes that potential issue.
$ uname -a
Linux arch_840 4.0.3-1-ARCH #1 SMP PREEMPT Wed May 13 15:38:47 CEST 2015 x86_64 GNU/Linux
$ lsmod | grep dm_
dm_crypt 28672 2
dm_mod 98304 5 dm_crypt
$ lsmod |grep xts
xts 16384 2 serpent_sse2_x86_64,twofish_x86_64_3way
gf128mul 16384 2 lrw,xts
smartctl status
Figured I should check the drive. There's a lot of old age and pre-fail warnings, but this post would seem to suggest I'm okay?
# smartctl -A /dev/sdb
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.3-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0
2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0
3 Spin_Up_Time 0x0023 090 089 025 Pre-fail Always - 3330
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 703
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 3707
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 104
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 734
191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 17
192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0
194 Temperature_Celsius 0x0002 064 053 000 Old_age Always - 24 (Min/Max 16/47)
195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 3
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 104
225 Load_Cycle_Count 0x0032 079 079 000 Old_age Always - 214068
Disk info, delete existing partition, new MBR, create new partition
# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.26.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x76d37b6d
Device Boot Start End Sectors Size Id Type
/dev/sdb1 63 976768064 976768002 465.8G 83 Linux
Command (m for help): d
Selected partition 1
Partition 1 has been deleted.
Command (m for help): o
Created a new DOS disklabel with disk identifier 0x2cd60f13.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-976773167, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-976773167, default 976773167):
Created a new partition 1 of type 'Linux' and of size 465.8 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
trying to format with cryptsetup
I had a bunch of custom options, but other Arch posts suggested just trying the default, which is what I've done here. It fails with the same error as when I try to pass a cipher, key size, etc. ("Command failed with code 5: IO error while encrypting keyslot.").
# truecrypt -v --debug luksFormat /dev/sdb1
bash: truecrypt: command not found
[root@arch_840 jwhendy]# cryptsetup -v --debug luksFormat /dev/sdb1
# cryptsetup 1.6.6 processing "cryptsetup -v --debug luksFormat /dev/sdb1"
# Running command luksFormat.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
WARNING!
========
This will overwrite data on /dev/sdb1 irrevocably.
Are you sure? (Type uppercase yes): YES
# Allocating crypt device /dev/sdb1 context.
# Trying to open and read device /dev/sdb1.
# Initialising device-mapper backend library.
# Timeout set to 0 miliseconds.
# Iteration time set to 1000 miliseconds.
# Interactive passphrase entry requested.
Enter passphrase:
Verify passphrase:
# Formatting device /dev/sdb1 as type LUKS1.
# Crypto backend (gcrypt 1.6.3) initialized.
# Detected kernel Linux 4.0.3-1-ARCH x86_64.
# Topology: IO (512/0), offset = 0; Required alignment is 1048576 bytes.
# Checking if cipher aes-xts-plain64 is usable.
# Using userspace crypto wrapper to access keyslot area.
# Generating LUKS header version 1 using hash sha1, aes, xts-plain64, MK 32 bytes
# KDF pbkdf2, hash sha1: 996745 iterations per second.
# Data offset 4096, UUID 181fed4d-42f2-4f0f-8b70-cb7ba459e25f, digest iterations 121625
# Updating LUKS header of size 1024 on device /dev/sdb1
# Key length 32, device size 976771120 sectors, header size 2050 sectors.
# Reading LUKS header of size 1024 from device /dev/sdb1
# Key length 32, device size 976771120 sectors, header size 2050 sectors.
# Adding new keyslot -1 using volume key.
# Calculating data for key slot 0
# KDF pbkdf2, hash sha1: 1008246 iterations per second.
# Key slot 0 use 492307 password iterations.
# Using hash sha1 for AF in key slot 0, 4000 stripes
# Updating key slot 0 [0x1000] area.
# Using userspace crypto wrapper to access keyslot area.
IO error while encrypting keyslot.
# Releasing crypt device /dev/sdb1 context.
# Releasing device-mapper backend.
# Unlocking memory.
Command failed with code 5: IO error while encrypting keyslot.
Things also tend to hang with respect to the drive at this point. For example, fdisk -l spits out /dev/sda partitions immediately and then just hangs instead of printing out /dev/sdb info, then eventually quits (without ever writing it).
Any suggestions on where to look/how to troubleshoot? I found some possibly related posts, but nothing that looks promising:
- Impossible to crypt the drive using cryptsetup (fixed by rebooting)
- cryptsetup fails to open Udev cookie 0xd4d94f5 (semid 0) waiting for z (no responses; the hang after seems similar)
There's a couple odds and ends references to cryptsetup 1.6.6 having issues. I downloaded 1.6.4-1 and 1.6.5-1 and -2 from ARM to try, but wanted to post this in the meantime in case something stuck out.
Last edited by jwhendy (2015-05-29 16:01:40)

@qinohe I thought of that and the other day started formatting with mkfs.ext4; unfortunately, it was at work and I had to leave before I could let it finish. It had been chugging along a good few hours, and I was surprised it would take that long. I was able to format it with ext4 using Windows 7 (I dual boot) with the MiniTool Partition Wizard but I didn't use it like that before trying to solve the cryptsetup issue again.
This last time around, I was getting unresponsive behavior. I think I need to reboot each time I try something with cryptsetup, as any commands related to that drive seem to hang afterwards (fdisk, umount, eject, mkfs, or trying crypsetup again). Perhaps I'll just let it cook overnight with mkfs and see if I can at least have an unencrypted, but functional drive.
One interesting tidbit is that even though cryptsetup fails, when I've tried to issue mkfs afterward, it asks me to confirm that I want to format the disk since it has a LUKS header... so something appears to have been written. Is it possible the header is causing some issues? I don't know much about the structure of a disk (like what range the MBR resides in, what constitutes a header, etc.) but have been wondering if there's some way to start really, really clean with the disk. Like I'd just bought it -- something appears to be lingering around from previous efforts?
@frostschutz I'll check tomorrow. That's a good question. Just checked journalctl and here are some of the errors that appear; unfortunately, I wasn't watching so I can't tell you what matches up with what command:
May 23 09:32:22 arch_840 systemd-udevd[7784]: inotify_add_watch(7, /dev/sdb1, 10) failed: No such file or directory
May 23 09:32:22 arch_840 kernel: usb 3-4: stat urb: status -108
### there's lots like this; like 10 in a row with various sector values listed
May 23 09:32:19 arch_840 kernel: Buffer I/O error on dev sdb1, logical block 61341696, lost async page write
May 23 09:32:19 arch_840 kernel: blk_update_request: I/O error, dev sdb, sector 490735616
### there's also a bunch like this, from tab #0 -> #29 (not colored red, so not sure they're errors?)
May 23 09:32:19 arch_840 kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 1d 07 bc 10 00 04 00 00
May 23 09:32:18 arch_840 kernel: sd 2:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
I paged down quite a ways and those seem like the unique messages when I search the journal for "sdb". Anything stand out? I will say that the same sector numbers appeared in multiple blocks of the third error type listed, so that makes me wonder if something is genuinely wrong with the disk. I'll post the output of the full smartctl scan when I hopefully run it tomorrow.
Thanks for chiming in!

Can't compile v4ldvb drivers with kernel 2.6.37

Compiling v4l from vanilla source gives this error message:
Kernel build directory is /lib/modules/2.6.37-ARCH/build
make -C /lib/modules/2.6.37-ARCH/build SUBDIRS=/home/mrmedia/source/v4l-dvb/v4l modules
make[2]: Entering directory `/usr/src/linux-2.6.37-ARCH'
/bin/sh: /sbin/lsmod: Filen eller katalogen finns inte
CC [M] /home/mrmedia/source/v4l-dvb/v4l/flexcop-i2c.o
/home/mrmedia/source/v4l-dvb/v4l/flexcop-i2c.c: In function 'flexcop_i2c_init':
/home/mrmedia/source/v4l-dvb/v4l/flexcop-i2c.c:253:39: error: 'I2C_CLASS_TV_DIGITAL' undeclared (first use in this function)
/home/mrmedia/source/v4l-dvb/v4l/flexcop-i2c.c:253:39: note: each undeclared identifier is reported only once for each function it appears in
make[3]: *** [/home/mrmedia/source/v4l-dvb/v4l/flexcop-i2c.o] Fel 1
make[2]: *** [_module_/home/mrmedia/source/v4l-dvb/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-2.6.37-ARCH'
make[1]: *** [default] Fel 2
make[1]: Leaving directory `/home/mrmedia/source/v4l-dvb/v4l'
make: *** [all] Fel 2
(Fel = Error)
I've really tried compilin all source and also minimizing the v4l modules to a bare minium for my cx88 chip on PCI, without Lirc support as well. Still same errors.
yaourt v4l-dvb-git compiles but gives these dmesg errors;
dmesg | grep cx88
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
So no working Hauppauge hvr-1300 DVB-T card. I have earlier successfully compiled these drivers under Ubuntu and kernel 2.6.33. As far as I know I have all dependencies and compilation tools installed - base-devel, kernel headers and so forth. I've done other yaourt compilations ok.
Googling gives that probably the kernel 2.6.37 and v4l-dvb source don't go together well, but I don't know how to go any further. What more can I do?
Last edited by swanson (2011-02-15 12:18:50)

Further tests:
Kernel 2.6.37-5-arch gives the error as well as kernel 2.6.37-6-arch;
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
cx88xx: Unknown symbol v4l2_i2c_new_subdev_cfg (err 0)
Compiling my own v4l from git does compile and load as dmesg confirms;
dmesg | grep cx88
cx88/0: cx2388x v4l2 driver version 0.0.8 loaded
cx8800 0000:01:07.0: PCI INT A -> Link[LNKB] -> GSI 18 (level, low) -> IRQ 18
cx88[0]: subsystem: 0070:9601, board: Hauppauge WinTV-HVR1300 DVB-T/Hybrid MPEG Encoder [card=56,autodetected], frontend(s): 1
cx88[0]: TV tuner type 63, Radio tuner type -1
cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.8 loaded
cx88[0]: i2c init: enabling analog demod on HVR1300/3000/4000 tuner
cx88[0]: hauppauge eeprom: model=96019
cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 18, latency: 64, mmio: 0xdd000000
wm8775 1-001b: chip found @ 0x36 (cx88[0])
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
cx88[0]/2: cx2388x 8802 Driver Manager
cx88-mpeg driver manager 0000:01:07.2: PCI INT A -> Link[LNKB] -> GSI 18 (level, low) -> IRQ 18
cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 18, latency: 64, mmio: 0xdb000000
cx88_audio 0000:01:07.1: PCI INT A -> Link[LNKB] -> GSI 18 (level, low) -> IRQ 18
cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
cx88/2: cx2388x dvb driver version 0.0.8 loaded
cx88/2: registering cx8802 driver, type: dvb access: shared
cx88[0]/2: subsystem: 0070:9601, board: Hauppauge WinTV-HVR1300 DVB-T/Hybrid MPEG Encoder [card=56]
cx88[0]/2: cx2388x based DVB/ATSC card
cx8802_alloc_frontends() allocating 1 frontend(s)
DVB: registering new adapter (cx88[0])
cx88/2: registering cx8802 driver, type: blackbird access: shared
cx88[0]/2: subsystem: 0070:9601, board: Hauppauge WinTV-HVR1300 DVB-T/Hybrid MPEG Encoder [card=56]
cx88[0]/2: cx23416 based mpeg encoder (blackbird reference design)
cx88[0]/2-bb: Firmware and/or mailbox pointer not initialized or corrupted
cx88[0]/2-bb: Firmware upload successful.
cx88[0]/2-bb: Firmware version is 0x02060039
cx88[0]/2: registered device video1 [mpeg]
BUT, the Hauppauge hvr -1300 doesn't work with scan, me-tv or kaffeine. All things seem to be present in /dev/;
ls /dev/dvb/adapter0
totalt 0
drwxr-xr-x 2 root root 120 20 feb 07.59 .
drwxr-xr-x 3 root root 60 20 feb 07.59 ..
crw-rw----+ 1 root video 212, 1 20 feb 07.59 demux0
crw-rw----+ 1 root video 212, 2 20 feb 07.59 dvr0
crw-rw----+ 1 root video 212, 0 20 feb 07.59 frontend0
crw-rw----+ 1 root video 212, 3 20 feb 07.59 net0
And I'm in the group video. So I guess the driver just don't work for my card. I'll have to start another thread about that.
Last edited by swanson (2011-02-20 08:55:07)

Database connecting error after kernel upgrade

Hi Gurus
I am tring to upgrade my system kernel from 144 to 179, the system based on AIX 6.1 and DB2 B9.5.2,
After upgrading kernel SAP is not starting and I found database connection error because which Database is not activated. The startdb command completed successfully. I found I/O error while trying to make db connection.
I am also tring make SAP up by using old kernel (backup) but getting same error for backup kernel also. Now my system is totaly down.
So please help me out if you have any idea for this error in db2 database. The start db logs are as given below.
Wed Jan 21 08:56:07 GMT+05:30 2009
LOGFILE FOR STARTING DB6 (DB2 UDB)
Wed Jan 21 08:56:07 GMT+05:30 2009
checking required environment variables
DB2INSTANCE is >db2d11<
INSTHOME     is >/db2/db2d11<
DB2DBDFT     is >D11<
Wed Jan 21 08:56:07 GMT+05:30 2009
starting database manager
01/21/2009 08:56:07     0   0   SQL1026N The database manager is already active.
SQL1026N The database manager is already active.
Database Manager started
SQL1036C An I/O error occurred while accessing the database. SQLSTATE=58030
Activate database failed
Wed Jan 21 08:56:08 GMT+05:30 2009
R3trans connect to the database
R3trans check finished with return code: 12
R3trans connect failed
Notify your SAP/database administrator
Wed Jan 21 08:56:08 GMT+05:30 2009
/usr/sap/D11/SYS/exe/run/startdb: Terminating with error code 2
Please help me out.
Regards,
Jayesh.

Hi Jayesh,
from your description I would guess that the IO error is not related to the kernel change at all.
Please have a look at db2diag.log for the real cause of the problem.
You should be able to reproduce the error with
db2 activate database <dbname>
Regards
               Frank

Vol_init failed (can't communicate with kernel)

Hi,
I'm running Sol 2.8 on a sparc SUNW, Sun blade 1000 and having problem
mounting the CDROM. I tried to start vold but
I'm seeing that /var/adm/messages is logging "vol_init
failed" and "Can't communicate with kernel". I've seen
similar error in the archive but no summary.
Pls help me on this....
Amit

check if the following daemon is running. Using command ps -ef | grep vold
if it isn't run the following command:
/etc/init.d/volmgt start
This will restart volume management and should automatically mount the cdrom whenb inserted into the drive

During upgrade I've had ERROR FATAL: kernel too old

I'm using a recompiled kernel 2.6, today I've upgraded my archlinux (like all days), but during it, I've had an error:
FATAL: kernel too old
Rebooting my computer, now I can't login on my archlinux, infact I've kernel panic (using default kernel). If instead I use my recompiled kernel, I can login, but wifi device is not more known, kde doesn't start more, nvidia drivers doesn't work. So it's impossible to login.
I've the same problem on another computer where I've archlinux with a recompiled kernel 2.6
Anyone has had the same problem or can show me a resolution ?
Please, I don't want reinstall completely Archlinux, infact I've it from 2 years and half on one computer, and from 1 year and half in the other.
Thanks.

Or prolly wiser would be to install the latest arch kernel...

EHP7 Upgrade with kernel 740 Sp37

Hi All,
We have done successfully upgrade from ERP 6.0 to EHP6 sp09 and Now we have decide to go with EHP7 update fro two scenerios 1. From ERP 6.0 (kernel 700) to ERP6.0 EHP7 (Kernel 740) and 2 ERP 6.0 to EHP6 sp09 (kernel 721_EXT) to ERP6.0 EHP7 (Kernel 740). . here I have Two queries.
1. -----------------------------------------------------------------------------------------------------------------
EHP7 for ERP6.0 with SP03
In that Mopz proposed EHP7 for ERP6.0 SP03 is available only for support pack update only. It suggest the note 1949802 which I am not able to get as MOPZ is still generating valid XML to update ERP6.0 EHP7 sp03
EHP7 for ERP6.0 with SP02
It gives the kernel 740 patch SP27, I was reading some SCN discussions of kernel SP27 is having some bugs and gives issue during preprocessing phase and update will have to reset. So I want to use Kernel 740 SP37, so how to achieve this as Mopz is not giving the option to select the latest kernel. I am afraid to modify the stack.xml file.
2. --------------------------------------------------------------------------------------------------------------------
One more query is in phase Extraction I got error "the new SAP tools in /usr/sap/MES/SUM/abap/exe cannot connect to your database".
Which I believe is because of SSFS is not configured in source kernel. So question is how to configure this for Kernel 740 at this stage (after extraction).
SAP Note 1622837 says if your source kernel is 7.0x then two options --- option b says start with SUM and after error in Extraction Install SSFS with kernel 7.40 that is already unpacked. So how can I configure the SSFS with 740 as source system kernel is still running under 700
Please help.
Regards
SS

Hi Guys,
While in downtime phase MAIN_NEWBAS/XPRAS_AIMMRG we are getting below
error.
2EETW152 Cannot open file "/usr/sap/MES/SUM/abap/data/R-
XXX13INCTSPLGN.SAP".
# /usr/sap/MES/SUM/abap/log/SAPR740XPRA90000145.MES
I have gone through the "sap note 1978218 - CTSPLUG 200 SP10 Upgrade
fails"
and implemented the same report to get sp09 data and cofiles of CTS
plugin. Both files got generated successfully and are available in
/usr/sap/MES/SUM/abap/data
File names are R-20009INCTSPLUG.SAP & D-20009INCTSPLUG.SAP
And cofiles name is K-20009INCTSPLUG.SAP
Then I continued with upgrade but it still fails with the same message.
I dont know why stack xml calculated the sp10 patch for CTS_PLUG while we were already on sp10
Anybody has idea on this.
Regards
Sukhwinder

Error with boot-archive - Machine completely corrupted

Hello!
About two weeks ago I installed the current Solaris Os on two v240 to form a cluster. For the first install I used ZFS, but that was incompatible with the cluster software. So I reinstalled the OS, chose "UFS" as the filesystem and mirrored all partitions onto the second drive in each machine with the Solaris Volume Manager.
Today I wanted to patch these machines and rebooted one of them into single user mode. Instead of booting correctly, I got this message:
WARNING: The following files in / differ from the boot archive:
changed /kernel/drv/did.conf
The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
"svcadm clear system/boot-archive"
{code}
So I booted the machine into failsafe mode and used the instructions from http://docs.sun.com/app/docs/doc/817-1985/gglbw?a=view to update the boot-archive. During this procedure I was confused that my first disk was listed as c0t0d0s0 and not c1t0d0s0. Also the output of metastat did not work and the system asked me if I wanted to mount a zpool which it found during startup. But there should not be any more zpool now, all partitions are UFS.
The reboot did not work with c0t0d0s0 in the vfstab, so I rebooted once again into failsafe. From this point, the whole system is corrupted. I am unable to boot anymore. The OpenBoot prompt tells me this:
[code]
Rebooting with command: boot
Boot device: disk File and args:
ERROR: Last Trap: Fast Data Access MMU Miss
{1} ok boot
ERROR: /pci@1c,600000: Last Trap: Fast Data Access MMU Miss
{1} ok
[/code]
I am unsure how to proceed from this point. The second machine tells me exactly the same error about "/kernel/drv/did.conf", so I do not think that in both servers a hard drive failed simultaniously.

Yeah, I posted a warning about a week ago about this issue.
If you have SVM mirrored root, then
following the "recommended actions" warnings that solaris gives in this situation results in a corrupted filesytem.
I have a job open with sun about it, and they have confirmed the problem..
From where you are, I recommend you rebuild the machines from scratch..
You might be able to split the mirror and fsck your way out, but its not worth the hassle.
I posted a way to "fix" the root cause of the issue, ie prevent the inconsistent boot archive in the first place yesterday in the "out of sync boot archive" thread in this forum.
So. you can avoid the problem the next time around..
What would have worked when it reported the inconsistent boot archive is to simply ignore it and do the "svcadm clear" command it mentions instead.
Then another reboot.
Alternatively, if you do the failsafe boot, make sure you rebuild the boot archive on both halves of the mirror..

MCE errors with kernel 2.6.32.x

Similar Messages

Maybe you are looking for