2.6.27 kernel is a DISASTER!!!

Please make this sticky.
To everyone who is lucky not to have upgraded to 2.6.27 kernel: DON'T! Contrary to the mainpage announcement this upgrade is NOT smooth. It breaks LOTS of crucial things for lots of people, like connectivity with some modems (including still widely used SpeedTouch 330), various USB devices not working, radeon drivers not working, systems becoming unbootable. FAR from smooth. AVOID AT ALL COSTS! Wait for bugs to get fixed.
I feel we are having a problem with kernels not receiving enough testing before being moved to core. Kernels need an order of magnitude more testing than anything else. We need a separate repository for testing kernels.

Please make this sticky.
Why? It's just a rant, nothing constructive.
To everyone who is lucky not to have upgraded to 2.6.27 kernel: DON'T!
Too late, I did it the second it hit [testing].
Contrary to the mainpage announcement this upgrade is NOT smooth.
It was smooth for me
It breaks LOTS of crucial things for lots of people, like connectivity with some modems (including still widely used SpeedTouch 330)
Don't have one, so I can't comment
, various USB devices not working,
All my usb stuff are working, external hd and usb sticks, 3 different cameras, a Palm, keyboard, mouse and a usb snake light
radeon drivers not working,
AMD/ATI's fault, not arch, 8.10 will work with kernel 2.6.27
systems becoming unbootable.
All my 4 boxes boots fine.
FAR from smooth. AVOID AT ALL COSTS! Wait for bugs to get fixed.
How about all the bugs that the 2.6.27 kernel do fix? Like 'SIGWINCH' ? And how about the new features, like the extra modes for ext4, and the UBIFS filesystem?
Edit: Seems like I'm not the only one that likes the new kernel
I feel we are having a problem with kernels not receiving enough testing before being moved to core.
So, why didn't you help out with the testing of the kernel?
Kernels need an order of magnitude more testing than anything else.
I can only partly agree with that one. There are a lot of other packages that are just as important, and way more error prone.
We need a separate repository for testing kernels.
toofishes wrote:What will that even accomplish besides even fewer folks using that repository and testing it?
+1
Last edited by Mr.Elendig (2008-10-17 00:17:23)

Similar Messages

MacBook pro no longer starts after a month of kernel panics. What to do?

After about a month of kernel panics, my Mac crashed one more time and will no longer start. It sits at a black screen and just beeps, sometimes once, three times or more. I've been waiting for a friend to bring me an osx startup disk so I can fix it from the disk utility, but in the meantime I've been avoiding suspect programs as well as starting the computer holding command + s and typing /sbin/fcsk fy as many people have told me, and each time it said my hard drive was all right. My friend is coming back this week with the disk, but I am afraid it will be impossible even to boot from that. Does anyone have any suggestions? I don't have apple care or a warranty so going to the nearest apple store (one hour away) or the nearest servicer (a few minutes away) doesn't seem good. What should I do? I'm also slightly worried because I installed a firmware update not long before the panics started, to get around the region limitations of the DVD drive. I'm hoping this didn't cause any problems, since these panics seem to be related to RAM but the timing is just too convenient. Could this be a factor?

Thanks again BDAqua, and sorry for the long delay between reponses. The computer's been out of sight and out of mind for me the past few weeks, but my wife reminded meabiut it this morning.
So I tried the repair disk function within disk utility on the install disc, and everything seemed to be ok. I got a message in green that says "the volume Jeffs OW Mac appears to be ok." And then "Volume repair complete." I also noticed that the capicity of the drive appeared to be 119.69 GB and the available space 119.61 GB, which I guess meant the drive was completely empty but working.
So I tried once again to restore from my time machine backup, and wonder of all wonders, it worked this time! Two hours of restoration later, I'm writing to you now from the restored computer, and my wife is thrilled (and thinks I'm a genius!). So thank you thank you thank you for taking the time to walk me through the steps! I really appreciate it!
But now we're afraid to try again to upgrade to Snow Leopard. Do you think there's any reason trying again would throw the computer into another state of confusion, flux, and ultimately disaster, or should I just give it a shot? It's a 2009 Macbook Pro 2.2 GHz Intel Core 2 Duo, with 2GB 667 MHz DDR2 SDRAM, running OS X 10.5.8. Perhaps it just can't handle the new software?
All the best, and thanks so much again!
Jeff

Frequent Kernel Panics on eMac OSX 10.3.9

Hi,
Sorry about the long post but am having a bit of a disaster so I'm providing as much information as possible, and have posted the panic log file as well:
This morning I installed the Billion BiPac 3012G Wireless USB adaptor and the related Mac 10.3 driver on my eMac. (there are no updates to this driver on the Billion website). It was working an absolute charm for a while, we connected to our airport network without a hitch - until I tried to adjust the settings for our network printer. Then I got the grey Kernel Panic screen (You need to restart).
I restarted and went through the same process (system prefs, printers and faxes, and double clicked on our network printer to adjust the settings) - and instantly got the same screen.
I restarted again and ran permissions verification and repair on the hard drive with no issue. Then as an added precaution I ran Cocktail (a disk utilities program) and as it was 'running the weekly cron reports' got the grey screen again. So I restarted, ran cocktail again - and got the grey screen at exactly the same point.
At this point I removed the new hardware.
I searched for panic.log and opened the most recent of the two files. As I was looking at it, grey screen again. After this I started getting the screen at frequent, random intervals.
Now I'm getting the restart screen frequently, even when I've left the computer alone with no programs open.
I reseated the ram in but that has not helped.
I've managed to get the log file off onto another computer, but I can't get it going long enough to uninstall the new driver or take any further troubleshooting methods.
Here is the log file - I'm hoping there might be someone out there who can decipher any of this and help me to understand what the problem is. Any suggestions would be greatly appreciated:
Tue Aug 26 10:27:13 2008
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000415C9C4C PC=0x0000000000069358
Latest crash info for cpu 0:
Exception state (sv=0x20464500)
PC=0x00069358; MSR=0x00009030; DAR=0x415C9C4C; DSISR=0x40000000; LR=0x00069260; R1=0x0CBF3CA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000004 0x00064928 0x00058998 0x00091074 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x20464500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20672500)
PC=0x8FE0541C; MSR=0x0000F030; DAR=0xA7509668; DSISR=0x42000000; LR=0x8FE05134; R1=0xBFFFE8E0; XCP=0x0000000C (0x300 - Data access)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x20464500)
PC=0x00069358; MSR=0x00009030; DAR=0x415C9C4C; DSISR=0x40000000; LR=0x00069260; R1=0x0CBF3CA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000004 0x00064928 0x00058998 0x00091074 0x0009402C
Exception state (sv=0x20672500)
PC=0x8FE0541C; MSR=0x0000F030; DAR=0xA7509668; DSISR=0x42000000; LR=0x8FE05134; R1=0xBFFFE8E0; XCP=0x0000000C (0x300 - Data access)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
Tue Aug 26 10:31:19 2008
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000415C9C4C PC=0x0000000000069358
Latest crash info for cpu 0:
Exception state (sv=0x20464500)
PC=0x00069358; MSR=0x00009030; DAR=0x415C9C4C; DSISR=0x40000000; LR=0x00069260; R1=0x0CBF3CA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000004 0x00064928 0x00058998 0x00091074 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x20464500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20672500)
PC=0x8FE0541C; MSR=0x0000F030; DAR=0xA7509668; DSISR=0x42000000; LR=0x8FE05134; R1=0xBFFFE8E0; XCP=0x0000000C (0x300 - Data access)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x20464500)
PC=0x00069358; MSR=0x00009030; DAR=0x415C9C4C; DSISR=0x40000000; LR=0x00069260; R1=0x0CBF3CA0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000004 0x00064928 0x00058998 0x00091074 0x0009402C
Exception state (sv=0x20672500)
PC=0x8FE0541C; MSR=0x0000F030; DAR=0xA7509668; DSISR=0x42000000; LR=0x8FE05134; R1=0xBFFFE8E0; XCP=0x0000000C (0x300 - Data access)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
Tue Aug 26 10:53:56 2008
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000004000004C PC=0x00000000001D51D8
Latest crash info for cpu 0:
Exception state (sv=0x1FAE2000)
PC=0x001D51D8; MSR=0x00009030; DAR=0x4000004C; DSISR=0x42000000; LR=0x001D5730; R1=0x0CB2B570; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x001D567C 0x000C2C44 0x000C2F10 0x000C0E34 0x001D5DA0 0x001D59D0 0x001DBB94 0x001DC288
0x000BEC44 0x000BE68C 0x000C83E4 0x00246D84 0x000941C0 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x1FAE2000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1FB5CA00)
PC=0x9775C74C; MSR=0x0000F030; DAR=0x20016F9C; DSISR=0x40000000; LR=0x977713B0; R1=0xBFFFFA40; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x1FAE2000)
PC=0x001D51D8; MSR=0x00009030; DAR=0x4000004C; DSISR=0x42000000; LR=0x001D5730; R1=0x0CB2B570; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x001D567C 0x000C2C44 0x000C2F10 0x000C0E34 0x001D5DA0 0x001D59D0 0x001DBB94 0x001DC288
0x000BEC44 0x000BE68C 0x000C83E4 0x00246D84 0x000941C0 0x00000000
Exception state (sv=0x1FB5CA00)
PC=0x9775C74C; MSR=0x0000F030; DAR=0x20016F9C; DSISR=0x40000000; LR=0x977713B0; R1=0xBFFFFA40; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
Tue Aug 26 10:56:18 2008
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000004000004C PC=0x00000000001D51D8
Latest crash info for cpu 0:
Exception state (sv=0x1FAE2000)
PC=0x001D51D8; MSR=0x00009030; DAR=0x4000004C; DSISR=0x42000000; LR=0x001D5730; R1=0x0CB2B570; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x001D567C 0x000C2C44 0x000C2F10 0x000C0E34 0x001D5DA0 0x001D59D0 0x001DBB94 0x001DC288
0x000BEC44 0x000BE68C 0x000C83E4 0x00246D84 0x000941C0 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x1FAE2000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1FB5CA00)
PC=0x9775C74C; MSR=0x0000F030; DAR=0x20016F9C; DSISR=0x40000000; LR=0x977713B0; R1=0xBFFFFA40; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x1FAE2000)
PC=0x001D51D8; MSR=0x00009030; DAR=0x4000004C; DSISR=0x42000000; LR=0x001D5730; R1=0x0CB2B570; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x001D567C 0x000C2C44 0x000C2F10 0x000C0E34 0x001D5DA0 0x001D59D0 0x001DBB94 0x001DC288
0x000BEC44 0x000BE68C 0x000C83E4 0x00246D84 0x000941C0 0x00000000
Exception state (sv=0x1FB5CA00)
PC=0x9775C74C; MSR=0x0000F030; DAR=0x20016F9C; DSISR=0x40000000; LR=0x977713B0; R1=0xBFFFFA40; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
Tue Aug 26 11:08:54 2008
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000040E175EC PC=0x0000000000069358
Latest crash info for cpu 0:
Exception state (sv=0x1F5ED280)
PC=0x00069358; MSR=0x00009030; DAR=0x40E175EC; DSISR=0x40000000; LR=0x00069260; R1=0x0CC5B7F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000310 0x0005FD90 0x0006014C 0x0026EF00 0x0026F018 0x0026EFDC 0x00462BBC 0x00460454
0x0044BE5C 0x0027E650 0x00280324 0x0007AC48 0x00021668 0x0001BCE8 0x0001C0F0 0x00094318
0x003C002F
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon8500(3.4.2)@0x445000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x398000
dependency: com.apple.iokit.IOGraphicsFamily(1.3.5)@0x40f000
dependency: com.apple.iokit.IONDRVSupport(1.3.5)@0x42f000
com.apple.iokit.IOSCSIArchitectureModelFamily(1.3.9)@0x3b7000
Proceeding back via exception chain:
Exception state (sv=0x1F5ED280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20022780)
PC=0x9774F878; MSR=0x0000F030; DAR=0x00764048; DSISR=0x40000000; LR=0x9774F3F8; R1=0xBFFEE4C0; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x1F5ED280)
PC=0x00069358; MSR=0x00009030; DAR=0x40E175EC; DSISR=0x40000000; LR=0x00069260; R1=0x0CC5B7F0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000310 0x0005FD90 0x0006014C 0x0026EF00 0x0026F018 0x0026EFDC 0x00462BBC 0x00460454
0x0044BE5C 0x0027E650 0x00280324 0x0007AC48 0x00021668 0x0001BCE8 0x0001C0F0 0x00094318
0x003C002F
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeon8500(3.4.2)@0x445000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x398000
dependency: com.apple.iokit.IOGraphicsFamily(1.3.5)@0x40f000
dependency: com.apple.iokit.IONDRVSupport(1.3.5)@0x42f000
com.apple.iokit.IOSCSIArchitectureModelFamily(1.3.9)@0x3b7000
Tue Aug 26 11:18:48 2008
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000040000088 PC=0x00000000001D4F6C
Latest crash info for cpu 0:
Exception state (sv=0x234D9A00)
PC=0x001D4F6C; MSR=0x00009030; DAR=0x40000088; DSISR=0x40000000; LR=0x001D4F30; R1=0x0CC43990; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x001D4F30 0x001D58D4 0x000DF6E4 0x000DF978 0x000BEC44 0x000BE68C 0x000CB2C8 0x00246D84
0x000941C0 0x003C002F
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOSCSIArchitectureModelFamily(1.3.9)@0x3b7000
Proceeding back via exception chain:
Exception state (sv=0x234D9A00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2C6C5780)
PC=0x97758C8C; MSR=0x0000F030; DAR=0x1FA50000; DSISR=0x42000000; LR=0x947F369C; R1=0xBFFFD750; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x234D9A00)
PC=0x001D4F6C; MSR=0x00009030; DAR=0x40000088; DSISR=0x40000000; LR=0x001D4F30; R1=0x0CC43990; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x001D4F30 0x001D58D4 0x000DF6E4 0x000DF978 0x000BEC44 0x000BE68C 0x000CB2C8 0x00246D84
0x000941C0 0x003C002F
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOSCSIArchitectureModelFamily(1.3.9)@0x3b7000
Exception state (sv=0x2C6C5780)
PC=0x97758C8C; MSR=0x0000F030; DAR=0x1FA50000; DSISR=0x42000000; LR=0x947F369C; R1=0xBFFFD750; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
Tue Aug 26 11:29:47 2008
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000042227C94 PC=0x0000000000038AA8
Latest crash info for cpu 0:
Exception state (sv=0x28B54C80)
PC=0x00038AA8; MSR=0x00009030; DAR=0x42227C94; DSISR=0x40000000; LR=0x00038A90; R1=0x0D363B70; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00068080 0x00069C2C 0x000632BC 0x00074ED0 0x0004DEB0 0x00021668 0x0001BCE8
0x0001C0F0 0x00094318 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x28B54C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x28F75C80)
PC=0x9774F878; MSR=0x0200F030; DAR=0x000F9EA0; DSISR=0x40000000; LR=0x9774F3F8; R1=0xBFFFF640; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x28B54C80)
PC=0x00038AA8; MSR=0x00009030; DAR=0x42227C94; DSISR=0x40000000; LR=0x00038A90; R1=0x0D363B70; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00068080 0x00069C2C 0x000632BC 0x00074ED0 0x0004DEB0 0x00021668 0x0001BCE8
0x0001C0F0 0x00094318 0x00000000
Exception state (sv=0x28F75C80)
PC=0x9774F878; MSR=0x0200F030; DAR=0x000F9EA0; DSISR=0x40000000; LR=0x9774F3F8; R1=0xBFFFF640; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
Thu Jan 1 10:00:28 1970
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000041C24F94 PC=0x00000000001EC074
Latest crash info for cpu 0:
Exception state (sv=0x28B51000)
PC=0x001EC074; MSR=0x00009030; DAR=0x41C24F94; DSISR=0x40000000; LR=0x002101F8; R1=0x0D6B3660; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x002101F8 0x0020EB3C 0x00246D84 0x000941C0 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x28B51000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x28B82000)
PC=0x9777F64C; MSR=0x0000F030; DAR=0x00004124; DSISR=0x40000000; LR=0x9779E2FC; R1=0xF0080A10; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x28B51000)
PC=0x001EC074; MSR=0x00009030; DAR=0x41C24F94; DSISR=0x40000000; LR=0x002101F8; R1=0x0D6B3660; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x002101F8 0x0020EB3C 0x00246D84 0x000941C0 0x00000000
Exception state (sv=0x28B82000)
PC=0x9777F64C; MSR=0x0000F030; DAR=0x00004124; DSISR=0x40000000; LR=0x9779E2FC; R1=0xF0080A10; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC

KPs are usually caused by a hardware problem - frequently RAM or USB devices. I don't think that the install of the drivers/hardware could cause a RAM problem. OS X is "pickey" about RAM quality. Look at this link: *Testing RAM* @ http://guides.macrumors.com/Testing_RAM
Then download & use Memtest & Ramber.
Also look at this link.12-Step Program to Isolate Freezes and/or Kernel Panics
 Cheers, Tom

What is the quickest to upgrade disaster recovery system to NW04s in MSCS?

Hi,
I have an issue which I need assistance from SAP/Windows 2003 experts.
Hope you can share your opinion on an SAP upgrade issue we're grappling with.
Objective : Upgrade our SAP Bank Analyzer disaster recovery environment from NW04 to NW04s SR2, to be same as production. Both production and disaster recovery (DR) run under two node WIN2003 Enterprise MSCS. The SAP CI usually runs on node A and Oracle 10g runs on node B.
The Oracle software, parameters, database files and the SAP folder \usr\sap are already matching. These files and folders are on EMC mirrored disks, so this will be automatically synchronized from production status.
Therefore I believe it is only the SAP software components on the local hard disks - binaries, DLLs, registry, DCOM, environment variable etc, that need to be upgraded on the two DR machines.
For your information, the current SAP 6.40 instance, Oracle 10g instance, MSCS failover capability are all working in the DR environment as we just did an exercise a month ago to prove this.
 Disaster Recovery Environment :
On shared drives that are synchronized between prod and DR : SAP folder \usr\sap including the kernel binaries, Oracle parameter files, database datafiles, redologs, sapbackup etc.
Issue : What is the quickest and reliable method to achieve the objective? Other than the SAP kernel binaries and profiles, I'm not certain what other related components are updated/replaced that are stored locally on each of the clustered machine.
There are three different approaches we can think of :
1) Repeat the whole NW04s upgrade process in the DR environment. This takes several days. The exposure of not having a disaster recovery environment for several days is a minus.
 or
2) Un-install the SAP CI and MSCS definitions. Synchronise the DR shared disks from production to have the upgraded production NW04s database contents and SAP folder \usr\sap.
Use SAPINST to re-install either traditional CI or ASCS option 'System Copy". And then re-create the MSCS definitions for SAP CI using SAPINST again.
The disadvantage is I can't trial this in any other of our environments. Also, we want to run with the traditional CI instead of ASCS until early next year for other reasons. So we would have to reverse the ASCS back to traditional CI with this method, by reversing the steps in OSS NOTE 101190 "Splitting CI after upgrade to 700".
 or
3) Somehow identify all the SAP components that are stored locally on each machine (eg. environment variables, registry settings, DCOM definitions, DLL in various folders). Then just copy them from Production to DR machines or recreate them. I'm not confident of identifying the local SAP components. And I have not been able to find any good OSS NOTEs or forum threads on this topic. The most helpful OSS NOTE I can find is 112266 point 13 and 19.
Thanks for any input.
Benny Kwan

See:
* https://support.mozilla.com/kb/Form+autocomplete
* Firefox > Preferences > Privacy > History: "Remember search and form history"
* Autofill Forms: https://addons.mozilla.org/firefox/addon/autofill-forms/

Kernel Panics, Drive Corruption, Directory Issues.

Desktop M8840LL/A Dual 1.25GHz PowerPC G4 (FW800) MDD
2GB Ram, 2 WD - 500GB IDE Drives Internal, 4 SATA Dr (2 WD - 500 GB SATA internal 1 WD 500GB SATA, One WD 640GB SATA external ), Sonnet Tempo SATA X4i PCI Card, ATI 9600Pro AGP, 1- 23in Apple Cinema Display, One 24in Samsung Display. 3 Firewire 250Gb WD external Drives.
This setup was running great for 2 years until a four year old WD drive failed 3 weeks ago and corrupted its data etc. I had the data backed up so no panic.
I decided to replaced it 3 weeks ago with a new 500GB WD IDE and reinstall 10.5 and migrate users for that drive.
Ever since I have been getting daily if not hourly kernel panics and issues with ALL drives on my system.
At one point the system loscked 4 drives and I could not access them at all.
Discussion group helped fix that issue.
I have managed to saved all my important data to a 500GB drive without a system on it and hopefully can deal with the issues at hand without worrying about the data.
Booted from my System 1.5 install disk and had a dark grey/ Must restart your mac screen while I was booting from the DVD!
Did an Apple Service diagnostics on the machine and all was great - no issues.
So I did a clean install on a drive and all looked great!
No other software installed except the system.
Rebooted OK.
I then did the apple software update and restarted.
No startup!
Rebooted with option key down - no drives??
I have been working on this for three days and seem to be going backwards at best.
I can boot sometimes and usually get a kernal panic eventually.
It can happen right away or an hour later.
Sometimes I get a message "your computer was shut down etc" sometimes I don't!?
Sometimes I get a startup chime - sometimes I don't!!??
What should I do next?
Advise whatever info you might need and I will do my best to provide it.

I stripped my Mac down to barebones incluing original 80GB Drive 512 RAM and Original Video card and started over.
To make a long procedure shorter I found that all hardware was OK and after running ASD to confirm I reinstalled all my hardware/Add ins except for drives.
I then started to check each drive individually with Applejack and then formatting and reinstalling virgin systems on each drive.
Applejack and/or the system DVD would not fix and/or install on three of the Hard Drives (1 IDE 500GB and 2 500GB SATA)due to permission corruption. I could not do anything with these drives at all!
When I had these individual drives in the computer I experienced kernel panics with every one!
All the drives were under warranty and Western Digital replaced all of them. (I cannot begin to tell you how great Western Digital was in turnaround time and cross shipping and help in this matter.) Their warranty service is the best I have ever experienced bar none!
I am now running non stop for nearly a week without any kernel panic or problem whatsoever. I have also noticed a significant speed up in my computer.
I have rebooted many times and run non stop for days at a time.
I maintain my computer with maintenance scripts once per week and do it faithfully and this type of permission issue can still occur!
Without my backups there would have been a disaster for me.
Many thanks to all the peolpe that emailed help to me from all sources.
Sometimes out of the worst of situations good prevails.

Kernel: PANIC! -- best practice for backup and recovery when modifying system?

I installed NVidia drivers on my OL6.6 system at home and something went bad with one of the libraries. On reboot, the kernel would panic and I couldn't get back into the system to fix anything. I ended up re-installing the OS to recovery my system.
What would be some best practices for backing up the system when making a change and then recovering if this happens again?
Would LVM snapshots be a good option? Can I recovery a snapshot from a rescue boot?
EX: File system snapshots with LVM | Ars Technica -- scroll down to the section discussing LVM.
Any pointers to documentation would be welcome as well. I'm just not sure what to do to revert the kernel or the system when installing something goes bad like this.
Thanks for your attention.

There is often a common misconception: A snapshot is not a backup. A snapshot and the original it was taken from initially share the same data blocks. LVM snapshot is a general purpose solution which can be used, for example, to quickly create a snapshot prior to a system upgrade, then if you are satisfied with the result, you would delete the snapshot.
The advantage of a snapshot is that it can be used for a live filesystem or volume while changes are written to the snapshot volume. Hence it's called "copy on write (COW), or copy on change if you want. This is necessary for system integrity to have a consistent data status of all data at a certain point in time and to allow changes happening, for example to perform a filesystem backup. A snapshot is no substitute for a disaster recovery in case you loose your storage media. A snapshot only takes seconds, and initially does not copy or backup any data, unless data changes. It is therefore important to delete the snapshot if no longer required, in order to prevent duplication of data and restore file system performance.
LVM was never a great thing under Linux and can cause serious I/O performance bottlenecks. If snapshot or COW technology suits your purpose, I suggest you look into Btrfs, which is a modern filesystem built into the latest Oracle UEK kernel. Btrfs employs the idea of subvolumes and is much more efficient that LVM because it can operate on files or directories while LVM is doing the whole logical volume.
Keep in mind however, you cannot use LVM or Btrfs with the boot partition, because the Grub boot loader, which loads the Linux kernel, cannot deal with LVM or BTRFS before loading the Linux kernel (catch22).
I think the following is an interesting and fun to read introduction explaining basic concepts:
http://events.linuxfoundation.org/sites/events/files/slides/Btrfs_1.pdf

Kernel startup failure and timeout error during J2EE startup

We are working on getting a DR (Disaster recovery) instance of EP6.0 started up after a restore from an offline backup of our Production Portal. This is on a separate piece of hardware. This is the J2EE version 6.2 and Ep 6.0 Sp2 Patch 37. This version is working fine on the Production Portal. When we start up the J2EE (using go.bat or the framework) we get the following error-
[OS: SunOS] [VM vendor: Sun Microsystems Inc.] [VM version: 1.3.1_11-b02] [VM type: Java HotSpot(TM) Client VM]
SAP J2EE Engine Version 6.20 PatchLevel 78993.20 is starting...
Loading: LogManager ...
Loading: SystemThreadManager ...
Loading: ThreadManager ...
Loading: TimeoutManager ...
Loading: MemoryManager ...
Loading: PoolManager ...
Loading: PolicyManager ...
Loading: IpVerificationManager ...
Loading: ClusterManager ...
Loading: ClassLoaderManager ...
Loading: SwapManager ...
Loading: LockManager ...
Loading: R3StartupManager ...
Loading: ServiceManager ...
Loading core services:
Starting core service monitor ... done. (215 ms)
Starting core service p4 ... done. (310 ms)
Starting core service log ... done. (447 ms)
Starting core service dbms ... done. (1145 ms)
Starting core service security ... done. (3008 ms)
Starting core service naming ... done. (5369 ms)
Starting core service admin ... done. (5616 ms)
Timeout starting core services. Kernel not started.
[ServiceManager]: * Timeout starting core services. Kernel not started.
Timeout starting core services.
Not started services:
deploy
file
[ServiceManager]:
Timeout starting core services.
Not started services:
deploy
file
Loading: ServiceManager returned false!
Kernel not loaded. System halted.
[Framework -> criticalShutdown] Kernel startup failed.
We need assistance as soon as possible.
Any pointers would help and will be greatly appreciated!
S. Rao

We resolved this error. It was a timeout setting that we needed to change on the J2EE that allowed it to bypass the timeout error.

Panic.log and Kernel Panic issues

Can anyone help me out with deciphering this kernel panic log. I've had about 4 KP's in the last couple months. I only have one in my log because I think that is the only one I have had since I did an erase and install. I checked it in for repair at an Apple Store where they ran a high load test on it and found no hardware problems nor could they determine the source of the KP's.
I have plently of disk space and a third party graphics card bought and installed at the Apple Store. The computer was used in a professional creative environment every day, 10 hours a day for a year and a half and was rarely shut down overnight. It was pushed pretty hard, was kept in an area that allowed for dust accumulation and the area below the desk where it was kept had pretty poor air flow. It was probably moved around a bit while running. All a recipe for disaster, but I figure it's better to be up front about it's condition before one were to help me out.
Beside the couple KP's I've had, it will occasionally hang up while switching into a different user while using "Fast User Switching". Aside from distinguishing what this log might mean, I am also curious to what degree a KP can have on further corruption of data. Data corruption concerns me more than the occasional KP that would force me to revert to my last save.
Here is the log file. Any help you can give would be appreciated.
-Tim
--------begin of panic.log-----------
Sat Jul 21 14:38:32 2007
Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000000000008 PC=0x000000000053FB4C
Latest crash info for cpu 1:
Exception state (sv=0x5F6BA500)
PC=0x0053FB4C; MSR=0x00009030; DAR=0x00000008; DSISR=0x42000000; LR=0x0053FD60; R1=0x459DB900; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0053FBF4 0x0053F9E0 0x00551658 0x0052EBC4 0x0052DE08 0x005532DC
0x0053FA90 0x0055190C 0x002D3B50 0x0003C884 0x000A9514
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOFireWireFamily(2.2.5)@0x527000
Proceeding back via exception chain:
Exception state (sv=0x5F6BA500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x5FC55000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.10.0: Wed May 23 16:50:59 PDT 2007; root:xnu-792.21.3~1/RELEASE_PPC
panic(cpu 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x000952D8 0x000957F0 0x00026898 0x000A8004 0x000AB980
Proceeding back via exception chain:
Exception state (sv=0x5F6BA500)
PC=0x0053FB4C; MSR=0x00009030; DAR=0x00000008; DSISR=0x42000000; LR=0x0053FD60; R1=0x459DB900; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0053FBF4 0x0053F9E0 0x00551658 0x0052EBC4 0x0052DE08 0x005532DC
0x0053FA90 0x0055190C 0x002D3B50 0x0003C884 0x000A9514
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOFireWireFamily(2.2.5)@0x527000
Exception state (sv=0x5FC55000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.10.0: Wed May 23 16:50:59 PDT 2007; root:xnu-792.21.3~1/RELEASE_PPC
--------end of panic.log-----------

Since it references com.apple.iokit.IOFireWireFamily, I suspect that some FW device is causing the panic. Disconnect all of them and see if that stops the problem. As for general KP stuff, start with http://www.thexlab.com/faqs/kernelpanics.html

Disaster recovery - Oracle

Hello!
Is there some simple step-by-step guide for disaster recovery of Enterprise 4.7, WAS 620, Oracle?
I am trying to create a disaster recovery scenario for our production based on DB13 backup and brrestore (I am doing backup to disk). The backup works fine and I have got the new machine to play with restore.
I am not very experienced BC and here's how my unsuccessfull try went on:
1. Installed the new SAP system on the "playground" machine with the file structure same as on production (the system was installed properly, I was able to log-on)
2. Stopped the new system and its database
3. messed a little with init<DBID>.sap until brrestore went on
4. brrestore-ed from the backed-up production files (the entire 'sapbackup' folder):
brrestore -b bdrfydrx.and -m full
; the brrestore run successfully and the files on the new system were replaced by the backed-up production files.
5. Attempted to run SAP: the processes were green for about 1 minute; however, I wasn't able to log on, and then the disp+work died (went not yellow, but rather grey)
6. Stopped the services
7. Replaced kernel with the production kernel (copied the entire 'usr' folder, shared the 'usr\sap' folder as saploc and sapmnt)
8. Attempt to start the services - it got even worse: the SAP<SAPSID>_<SYSNO> service wouldn't start. The popup says that the service returns no error, but it's rather a Windows or internal service error.
And now I'm stuck. Please help! The SAP notes on this matter (such as 96848 - Disaster recovery for SAP R/3 on Oracle) have endless iterations of reference notes, and are not very tutorial-organized. The Installation Guide "Homogeneous and Heterogeneous System Copy..." includes only copy based on running SAPinst to export the database, not on backup/restore.
Is there something better?
Thanks in advance!
Kind regards,
Igor
P.S. If I survive, I promise to write a "restore for dummies" weblog on this.

Hello,
Here is the guide:
http://help.sap.com/saphelp_nw04s/helpdata/en/72/96d34c435c3c4ca5894749ef1435ac/frameset.htm
Also,
I thought after you restroed the brrestore backup, you need to recover you database by restoring all your redo log files to the target server and issuing the command in sqlplus:
recover database until cancel auto;
Can you paste your alert log ?
Regards,
Siddhesh

Unresolved Kernel Trap - can't restart after reinstalling OS

hi, i just zeroed out one partition on my G5 after backing up the files to another partition. i wanted to reinstall a clean OS. i wasn't able to install from the CD in the G5 - kept getting a weird broken apple logo and the computer fan would start to rev. - so i reinstalled from the original discs but had to do so from my iMac G5 with the G5 connected as a FW drive. here the install went fine and i was even able to boot from the newly installed OS as well as the backuped up system from my iMac G5.
however the problem starts when i disconnect the G5 and reboot it. the OS starts to load, i see the apple logo but then a dark grey screen descends and i am told i must restart the computer. the text on the screen says "Unresolved Kernal Trap (cpu 0)" followed by more info that i don't understand.
i can't seem to boot. i checked the prermissions by hooking back up in FW mode to the iMac and apparently there were some issues which disc utility resolved. still i can't restart the G5.
the hardware configuration i have is identical to what i had when the unit arrived a year ago.
can anyone please offer me a solution?
thx

Hello I am having a very similar problem. I am running a G5 with two drives.I haven't used the drive the computer came with as I transferred the drive from an older g5 into the #2 slot and have been working from that.(OSX Tiger upgraded from Panther)
I purchased some new software so decided to do a clean install on the newer drive (Purchased with OSX Tiger installed.)
I cannot find my original install CD's which came with the machine(I know I'm an idiot) so I tried the install from my Tiger CD.Every time I tried to restart with the CD I got the unresolved Kernel disaster described above.Luckily I managed to boot up the computer on the old drive by resetting the PRAM as I started up.
I called the local Apple shop and he advised creating a disc image of the CD and from that navigating to System/installation/packages/OSinstall.mpkg and installing from there. I had a little trouble figuring out how to create a disc image from the CD so navigated to the above installer within the CD itself,opened the installer which then proceeded to successfully install the OS on the erased drive."I'm saved" I yell! BUT when I try to boot up the newly installed OS I get the same unresolved kernel thingo.
But wait there's more,now I can't boot up at all,not even using the PRAM trick.
Remember I don't have the Discs that came with the machine to boot up with.
Am I totally screwed?
Any help would be greatly appreciated
Cheers
Brandon

Kernel panic - OsX 10.7.4

I upgraded my system (mac mini mid 2011 with AMD card) to 10.7.4 and after logging in and playing with it around 15 or 20 minutes, my mac starts to hang. This is the logs after the disaster.
Interval Since Last Panic Report: 708 sec
Panics Since Last Report:          4
Anonymous UUID:                    AEF15719-21DD-4EDB-A708-F428F568D100
Fri Aug 31 21:22:33 2012
panic(cpu 2 caller 0xffffff800027e24c): "VMSEL: INSERT FAILED: 0x123b68000, 0x123c43000, 0x123b68000, 0x123bf1000"@/SourceCache/xnu/xnu-1699.26.8/osfmk/vm/vm_map_store_rb.c:106
Backtrace (CPU 2), Frame : Return Address
0xffffff807ff4ba40 : 0xffffff8000220792
0xffffff807ff4bac0 : 0xffffff800027e24c
0xffffff807ff4bae0 : 0xffffff800027cc14
0xffffff807ff4bb10 : 0xffffff8000279a71
0xffffff807ff4bc50 : 0xffffff800027c355
0xffffff807ff4bd20 : 0xffffff8000546cc9
0xffffff807ff4bf50 : 0xffffff80005cd61b
0xffffff807ff4bfb0 : 0xffffff80002daa13
BSD process name corresponding to current thread: Software Update
Mac OS version:
11E53
Kernel version:
Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64
Kernel UUID: A8ED611D-FB0F-3729-8392-E7A32C5E7D74
System model name: Macmini5,2 (Mac-4BC72D62AD45599E)
System uptime in nanoseconds: 710293632774
last loaded kext at 73783041284: com.apple.driver.AppleBluetoothMultitouch          70.12 (addr 0xffffff7f81f00000, size 73728)
last unloaded kext at 148592059583: com.apple.driver.AppleUSBUHCI          4.4.5 (addr 0xffffff7f80a34000, size 65536)
loaded kexts:
foo.tap          1.0
foo.tun          1.0
com.apple.driver.AppleBluetoothMultitouch          70.12
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.driver.AudioAUUC          1.59
com.apple.driver.ApplePlatformEnabler          2.0.5d2
com.apple.driver.AGPM          100.12.42
com.apple.filesystems.autofs          3.0
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.driver.AppleHDA          2.2.0f3
com.apple.driver.AppleMikeyDriver          2.2.0f3
com.apple.driver.AppleUpstreamUserClient          3.5.9
com.apple.driver.AppleMCCSControl          1.0.26
com.apple.kext.ATIFramebuffer          7.1.8
com.apple.driver.AppleIntelHD3000Graphics          7.1.8
com.apple.driver.AppleSMCPDRC          5.0.0d0
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.iokit.IOBluetoothSerialManager          4.0.5f11
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AudioIPCDriver          1.2.2
com.apple.driver.ACPI_SMC_PlatformPlugin          5.0.0d0
com.apple.driver.AppleLPC          1.5.8
com.apple.ATIRadeonX3000          7.1.8
com.apple.driver.BroadcomUSBBluetoothHCIController          4.0.5f11
com.apple.driver.AppleIRController          312
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          33
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.0.3
com.apple.driver.AppleFWOHCI          4.8.9
com.apple.driver.AppleUSBHub          4.5.0
com.apple.driver.AppleEFINVRAM          1.5.0
com.apple.driver.AirPort.Brcm4331          530.4.20
com.apple.driver.AppleSDXC          1.2.0
com.apple.iokit.AppleBCM5701Ethernet          3.1.2b2
com.apple.driver.AppleAHCIPort          2.3.0
com.apple.driver.AppleUSBEHCI          4.5.8
com.apple.driver.AppleACPIButtons          1.5
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleHPET          1.6
com.apple.driver.AppleSMBIOS          1.8
com.apple.driver.AppleACPIEC          1.5
com.apple.driver.AppleAPIC          1.5
com.apple.driver.AppleIntelCPUPowerManagementClient          193.0.0
com.apple.nke.applicationfirewall          3.2.30
com.apple.security.quarantine          1.3
com.apple.driver.AppleIntelCPUPowerManagement          193.0.0
com.apple.driver.AppleMultitouchDriver          231.4
com.apple.driver.AppleBluetoothHIDKeyboard          160.7
com.apple.driver.AppleHIDKeyboard          160.7
com.apple.driver.IOBluetoothHIDDriver          4.0.5f11
com.apple.kext.triggers          1.0
com.apple.driver.DspFuncLib          2.2.0f3
com.apple.driver.AppleSMBusController          1.0.10d0
com.apple.iokit.IOSurface          80.0.2
com.apple.iokit.IOFireWireIP          2.2.4
com.apple.iokit.IOSerialFamily          10.0.5
com.apple.driver.AppleHDAController          2.2.0f3
com.apple.iokit.IOHDAFamily          2.2.0f3
com.apple.iokit.IOAudioFamily          1.8.6fc17
com.apple.kext.OSvKernDSPLib          1.3
com.apple.driver.ApplePolicyControl          3.0.16
com.apple.driver.AppleGraphicsControl          3.0.16
com.apple.driver.AppleSMC          3.1.3d8
com.apple.driver.IOPlatformPluginLegacy          5.0.0d0
com.apple.driver.AppleSMBusPCI          1.0.10d0
com.apple.driver.IOPlatformPluginFamily          5.1.0d17
com.apple.iokit.IONDRVSupport          2.3.2
com.apple.kext.ATI6000Controller          7.1.8
com.apple.kext.ATISupport          7.1.8
com.apple.driver.AppleIntelSNBGraphicsFB          7.1.8
com.apple.iokit.IOGraphicsFamily          2.3.2
com.apple.iokit.IOSCSIArchitectureModelFamily          3.2.0
com.apple.driver.AppleThunderboltDPOutAdapter          1.8.2
com.apple.driver.AppleThunderboltDPInAdapter          1.8.2
com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.2
com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.4
com.apple.driver.AppleUSBBluetoothHCIController          4.0.5f11
com.apple.iokit.IOBluetoothFamily          4.0.5f11
com.apple.iokit.IOUSBHIDDriver          4.4.5
com.apple.driver.AppleUSBComposite          4.5.8
com.apple.driver.AppleThunderboltNHI          1.5.5
com.apple.iokit.IOThunderboltFamily          2.0.0
com.apple.iokit.IOFireWireFamily          4.4.5
com.apple.iokit.IOUSBUserClient          4.5.8
com.apple.iokit.IO80211Family          420.3
com.apple.iokit.IOEthernetAVBController          1.0.1b1
com.apple.iokit.IONetworkingFamily          2.1
com.apple.iokit.IOAHCIFamily          2.0.8
com.apple.driver.AppleEFIRuntime          1.5.0
com.apple.iokit.IOUSBFamily          4.5.8
com.apple.iokit.IOHIDFamily          1.7.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          177.5
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.DiskImages          331.6
com.apple.iokit.IOStorageFamily          1.7.1
com.apple.driver.AppleKeyStore          28.18
com.apple.driver.AppleACPIPlatform          1.5
com.apple.iokit.IOPCIFamily          2.6.8
com.apple.iokit.IOACPIFamily          1.4
Model: Macmini5,2, BootROM MM51.0077.B10, 2 processors, Intel Core i5, 2.5 GHz, 4 GB, SMC 1.75f0
Graphics: AMD Radeon HD 6630M, AMD Radeon HD 6630M, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0198, 0x393930353432382D3035312E4130304C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE4), Broadcom BCM43xx 1.0 (5.106.198.4.20)
Bluetooth: Version 4.0.5f11, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8281, 0xfa113000 / 6
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
I did not install anything except Skype.
Do you know how to fix this frustrated problem?

loaded kexts:
foo.tap          1.0
foo.tun          1.0
Message was edited by: hpr3

Kernel Parameter (to do or not to do)

I have seen numerous threads about the Kernel Parameters, however
there seem to be a disagreement if it should be modified on Linux
or if it should not be modified.
Does anyone knows has an answer on this one. If it has to be
modified in the /usr/include/asm/shmparam.h file what are the
exact changes to be done. For example, there is no SHMMNI
define in that file, do I simply add the SHMMNI or what else.
Thanks
Clement
null

When everything is running well is the time to update.
Updating when your Mac is having problems is a recipe for disaster and then you arrive at this worldwide online hospital for sick Macs
Back up > Remove iPods, spare HDs and assorted peripherals > Download Combo updater from Apple > Restart > Then install and be patient through two Automatic restarts.
No problems here.

Aspell upgrade leads to - FATAL: kernel too old - SYSTEM BACK UP 8-)

OK, I really hosed it up now 8-(
Who would think that upgrading a spellchecker could cause such a problem, but upgrading aspell has totally crashed my system.
I knew something was fishy when it wanted to change all of the gcclibs, but I went ahead and --force 'd the upgrade anyway. What a schmuck!
It brings something to mind about too much rope.
Now I can't run any command without it leading to -> FATAL: kernel too old
I can't pacman back to the older package, I can't manually cp the files, WTF?!
Seems like the kernel itself should have been a dependancy.
It looks like I'm rescue CD bound at this point.
Any insight as to what to repair first would be GREATLY appreciated.
The command line session that led to this little disaster is included below.
It's interesting that the programs that were already running will still run (the shell still runs, it just can't launch any new programs, even ls, mv, etc.) I'm even making this post from the browser that was running prior to the debacle, but I can't ls, wow.
Thanks again for any insight...
android
~~~~~~~~~~~~~~~~~ here's what happened ~~~~~~~~~~~~~~~~~~~~~~
root@recube johnea]# pacman -S aspell
resolving dependencies... done.
looking for inter-conflicts... done.
Targets: kernel-headers-2.6.22.1-1 glibc-2.6.1-2 gcc-libs-4.2.1-2 aspell-0.60.5-2
Total Package Size: 13.14 MB
Proceed with installation? [Y/n]
:: Retrieving packages from current...
kernel-headers 611.0K 435.1K/s 00:00:01 [####################################################] 100%
glibc 10.6M 899.7K/s 00:00:12 [####################################################] 100%
gcc-libs 1079.3K 568.4K/s 00:00:02 [####################################################] 100%
:: Retrieving packages from extra...
aspell 877.5K 508.8K/s 00:00:02 [####################################################] 100%
checking package integrity... done.
cleaning up... done.
(4/4) checking for file conflicts [####################################################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
gcc-libs: /usr/lib/libgcc_s.so exists in filesystem
gcc-libs: /usr/lib/libgcc_s.so.1 exists in filesystem
gcc-libs: /usr/lib/libgomp.a exists in filesystem
gcc-libs: /usr/lib/libgomp.so exists in filesystem
gcc-libs: /usr/lib/libgomp.so.1 exists in filesystem
gcc-libs: /usr/lib/libgomp.so.1.0.0 exists in filesystem
gcc-libs: /usr/lib/libgomp.spec exists in filesystem
gcc-libs: /usr/lib/libmudflap.a exists in filesystem
gcc-libs: /usr/lib/libmudflap.so exists in filesystem
gcc-libs: /usr/lib/libmudflap.so.0 exists in filesystem
gcc-libs: /usr/lib/libmudflap.so.0.0.0 exists in filesystem
gcc-libs: /usr/lib/libmudflapth.a exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so.0 exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so.0.0.0 exists in filesystem
gcc-libs: /usr/lib/libssp.a exists in filesystem
gcc-libs: /usr/lib/libssp.so exists in filesystem
gcc-libs: /usr/lib/libssp.so.0 exists in filesystem
gcc-libs: /usr/lib/libssp.so.0.0.0 exists in filesystem
gcc-libs: /usr/lib/libssp_nonshared.a exists in filesystem
gcc-libs: /usr/lib/libstdc++.a exists in filesystem
gcc-libs: /usr/lib/libstdc++.so exists in filesystem
gcc-libs: /usr/lib/libstdc++.so.6 exists in filesystem
gcc-libs: /usr/lib/libstdc++.so.6.0.9 exists in filesystem
gcc-libs: /usr/lib/libsupc++.a exists in filesystem
gcc-libs: /usr/share/locale/de/LC_MESSAGES/libstdc++.mo exists in filesystem
gcc-libs: /usr/share/locale/fr/LC_MESSAGES/libstdc++.mo exists in filesystem
errors occurred, no packages were upgraded.
[root@recube johnea]#
[root@recube johnea]# pacman -S --force aspell
resolving dependencies... done.
looking for inter-conflicts... done.
Targets: kernel-headers-2.6.22.1-1 glibc-2.6.1-2 gcc-libs-4.2.1-2 aspell-0.60.5-2
Total Package Size: 13.14 MB
Proceed with installation? [Y/n]
checking package integrity... done.
cleaning up... done.
(1/4) upgrading kernel-headers [####################################################] 100%
(2/4) upgrading glibc [####################################################] 100%
FATAL: kernel too old
(3/4) installing gcc-libs [####################################################] 100%
(4/4) upgrading aspell [####################################################] 100%
FATAL: kernel too old
FATAL: kernel too old
[root@recube johnea]# ls -l /var/cache/pacman/pkg/ | grep gcc
FATAL: kernel too old
FATAL: kernel too old
[root@recube johnea]# ls
FATAL: kernel too old
[root@recube johnea]# pacman
FATAL: kernel too old
[root@recube johnea]#
Last edited by android (2007-10-10 04:54:58)

Thanks JGC!
After booting from a rescue CD, I was able to pacman -U to the 2.5 version of glibc and the appropriate kernel-headers and now I'm back in action.
This machine was setup about 2 years ago. At that time I built my own kernel in order to get all of my motherboard features to work.
I've been running arch as my primary desktop workstation for almost 5 years now. I've never really had luck using the pacman -Su option. There always seems to be some inter dependency issue that prevents it from completing.
For instance, after recovering from this current dillema (and backing up my home/ 8-) I thought I'd abandon my custom kernel and launch forward into stock arch.
The pacman -Su led to this isssue:
:: ttf-bitstream-vera conflicts with xorg. Remove xorg? [Y/n] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: ttf-bitstream-vera: conflicts with xorg
Now, I don't have a package installed called ttf-bitstream-vera, but apparently pacman thinks I need it and I can't have it and xorg at the same time.
Some variant of this situation occurs each time I've tried to use the upgrade feature of pacman through the years.
Now I know some people have never reinstalled their systems from sctratch for years by continuously using pacman -Su and just staying up to date. But this just hasn't worked for me. Each time something goes wrong, sometimes leaving me with a system that takes days to get back into working order.
This current issue, while being inconvenient in having to use a rescue CD to recover, wasn't that hard to overcome. I've done pacman -U to older versions numerous times to get out of problems caused by upgrading a specific package. However when a complete system upgrade goes bad, it's very difficult to discover what has to be downgraded to get back to the working system.
But, I'm willing to try again.
Any insight into why the ttf-bitstream-vera package should conflict with xorg would be very much appreciated.
I'm looking into setting pacman.conf to prevent ttf-bitstream-vera from being loaded at all. This is my current workaround approach. Once everything is upgraded perhaps these fonts will load without error.
As usual, things aren't as simple as one might first suspect.
Thanks again for your help!
android

CPU load higher after applying in 147440 kernel on Oracle database servers

Hi all,
Just wanted to know if anyone else is seeing an Increased CPU load with higher peaks and for longer periods of time, especially on single thread processes on oracle database servers. Our Oracle Database versions vary from Oracle 10 to Oracle 11.1.0.7 11.2.0.2 10.2.0.4. The Hardware includes Sunfire V245's, V440 and T5240. We saw a slight performance hit when going to 147440-02 at the first of Oct, but no big deal. Then we applied 147440-04 in the first part of Nov. And of course we got CPU panics and Zfs file system stopped mounting basically a complete disaster. Oracle provided and IDR for the CPU panic and then later release 147440-06. Which resolved the CPU panics and zfs file system mounts. But now our load average on is 1 to 3 points higher during load, grid control is constantly complaining of 100% utilization. I have had a call open since the first of November with oracle/sun support and have provided guds performance stats on before and after Kernel change. They are still saying that its not an issue. It is so bad we had to roll back to a July kernel on one of the servers.

Just to let you all know what we have found. After 2 1/2 months of working with Oracle Kernel team, they have identified the Oracle Enterprise Manager (emagent) (Grid control Agent) was using nearly 60000 threads under the 147440 Kernel and only 1500 threads under an older kernel.
I googled the solution for the emagent, but I continue to press Oracle Kernel Engineers to work with their software division, to identify other products that might cause similar problems.
http://oracle-dba-quickanswers.blogspot.com/2011/10/emagent-consuming-very-high-cpu.html

Kernel panic when changing settings

I have had my Macbook for 3 weeks now, and have had only one issue with it (the flickering caps/num lock keys) but didn't worry to much about it.. Then I got a kernel panic this morning.
I was changing the settings of sound input from line in to built-in microphone and the input level, and pressed command+Q to get out of system preferences, and got a kernel panic instantly. I know there has been many issues with headphones and macbooks, but this seemed different.
I am considering getting this thing replaced, as i rely on this computer through my work, and it would be a disaster to experience this on a regularily basis.
Any suggestions?
Macbook 2.0|2gb mem|80gb Mac OS X (10.4.7)

I have had my Macbook for 3 weeks now, and have had only one issue with it (the flickering caps/num lock keys) but didn't worry to much about it.. Then I got a kernel panic this morning.
I was changing the settings of sound input from line in to built-in microphone and the input level, and pressed command+Q to get out of system preferences, and got a kernel panic instantly. I know there has been many issues with headphones and macbooks, but this seemed different.
I am considering getting this thing replaced, as i rely on this computer through my work, and it would be a disaster to experience this on a regularily basis.
Any suggestions?
Macbook 2.0|2gb mem|80gb Mac OS X (10.4.7)

2.6.27 kernel is a DISASTER!!!

Similar Messages

Maybe you are looking for