System facing kernel panic....

I was updating my sysem with OS Maverick but it suddenly restarted and now only disk utility window is opening.
I hav't taken the recent backup through any means. I know thats stupid but I did so.
I tried almost all ways to restore but failed. Please help me out with this.

Thanks. That means you have booted into Recovery: http://support.apple.com/kb/ht4718
First, try resetting NVRAM/PRAM by shutting down, then restart holding down these four keys, command, option, p, r
Hold them until you hear the startup tone twice.
If it boots into recovery again, choose Disk Utility
Select your hard drive and the First Aid tab
Click Repair Disk (not permissions).
If it finds any errors, run the repair again until it doesn't report any and says disk is ok.
Make sure the Startup Disk is set to your hard drive. I can't remember where that is but it is either in the Disk Utility menu, or it is in the Main menu in Recovery once you quit disk utility.

Similar Messages

System Hang, kernel panic.

Hello list,
Doing some independent research into an issue we are having here. We have 21 x4540s running 5.10 Generic_141445-09. They are used as NFSv4 servers to front-end servers. The x4540s that are used for mail (postfix+dovecot) periodically hang. The others do not.
Since they hang, it has been difficult to diagnose what the issue could be. We have "set pcplusmp:apic_panic_on_nmi=1" in /etc/system, and I try to issue "set generate_host_nmi = true" in ILOM, but it appears to be too dead to manage that.
The only symptoms we have in the logs are:
Jul 24 07:50:49 x4500-11.unix inetd[292]: [ID 702911 daemon.error] Unable to fork inetd_start method of instance svc:/network/nfs/rquota:default: Resource temporarily unavailable
Jul 24 07:51:09 x4500-11.unix last message repeated 1 time
Jul 24 07:51:15 x4500-11.unix sshd[343]: [ID 800047 auth.error] error: fork: Error 0
Jul 24 07:54:25 x4500-11.unix last message repeated 4 times
A few times I have had a working shell connected when it happened, still running top, which shows it is not out of memory, not even close. No process has gone wild (pretty much just nfsd running). It would appear that it can't start new processes, but not due to lack of memory. Eventually it grinds down to a halt, including console. If I try to run "reboot" (or even reboot -d) it tries to reboot, but fails (just hangs). ILOM reset /SYS will bring it all back again.
Currently, this happens 2-3 times a month. Funnily enough, always at night. What does run at night is a recursive zfs snapshot. It usually dies sometime after that. The process that always gets the first error is rquotad. But that could just be because it is constantly queried.
Not much to go on alas.
Then one day, we got a panic dump. Is it the same problem, or something unrelated? Hard to know, but IF it were to be related...
::statusdebugging crash dump vmcore.0 (64-bit) from x4500-13.unix
operating system: 5.10 Generic_144489-10 (i86pc)
panic message: BAD TRAP: type=8 (#df Double fault) rp=ffffffffc4abff10 addr=0
dump content: kernel pages only
::showrevHostname: x4500-13.unix
Release: 5.10
Kernel architecture: i86pc
Application architecture: amd64
Kernel version: SunOS 5.10 i86pc Generic_144489-10
Platform: i86pc
$<msgbufMESSAGE
fffffe80010a2ca8 dtrace:dtrace_dynvar+730 ()
>> warning! 8-byte aligned %fp = fffffe80010a2d78
fffffe80010a2d78 dtrace:dtrace_dynvar+730 ()
>> warning! 8-byte aligned %fp = fffffe80010a2e48
......snip...
>> warning! 8-byte aligned %fp = fffffe80010a5948
fffffe80010a5948 dtrace:dtrace_probe+606 ()
>> warning! 8-byte aligned %fp = fffffe80010a5968
fffffe80010a5968 fbt:fbt_invop+a8 ()
>> warning! 8-byte aligned %fp = fffffe80010a5998
fffffe80010a5998 unix:dtrace_invop+3b ()
fffffe80010a5ae0 unix:invoptrap+108 ()
fffffe80010a5b30 genunix:fop_getpage+47 ()
fffffe80010a5d00 genunix:segvn_fault+8b0 ()
fffffe80010a5dc0 genunix:as_fault+205 ()
fffffe80010a5e20 unix:pagefault+8b ()
fffffe80010a5f00 unix:trap+3d7 ()
fffffe80010a5f10 unix:cmntrap+140 ()
::panicinfo             cpu                9
          thread fffffe88e5265180
         message BAD TRAP: type=8 (#df Double fault) rp=ffffffffc4abff10 addr=0
             rdi fffffe8f5496fa70
             rsi                2
             rdx fffffe80010a5768
fffffe88e5265180::walk thread fffffe8946f791e8
mdb: failed to read thread at 100000000: no mapping for address
::psS    PID   PPID   PGID    SID    UID      FLAGS             ADDR NAME
R      0      0      0      0      0 0x00000001 fffffffffbc273c0 sched
R     77      0      0      0      0 0x00020001 ffffffffc9e73c80 zpool-zpool1
R      3      0      0      0      0 0x00020001 ffffffffc1f86e10 fsflush
R      2      0      0      0      0 0x00020001 ffffffffc1f87a78 pageout
R      1      0      0      0      0 0x4a004000 ffffffffc1f886e0 init
R 17651      1 17651 17635      0 0x4a014000 fffffe88d4b8e030 bash
R 14059 17651 17651 17635      0 0x4a004000 fffffe8ab1817e60 head
R 14058 17651 17651 17635      0 0x4a004000 fffffe8946f791e8 sort
R 14057 17651 17651 17635      0 0x4a004000 fffffe88dc9aa040 awk
R 14056 17651 17651 17635      0 0x4a004000 ffffffffc5a9f6e8 ps
R   3534      1   3534   3508      0 0x4a014000 fffffe8ab126dcb8 bash
R   3535   3534   3535   3508      0 0x4a004000 fffffe88dc9b6710 dtrace
R    431      1    431    431      0 0x42000000 fffffe88dc9b2908 fmd
R    458      1    458    458 60001 0x52000000 fffffe88d4b95028 nrpe
R    441      1    441    441     25 0x52010000 fffffe88dc9b1ca0 sendmail
R    440      1    439    439      0 0x42000000 fffffe88dc9aeab0 snmpd
R    438      1    438    438      0 0x42000000 fffffe88dc9ad1e0 dmispd
R    424      1    424    424      1 0x42000000 fffffe88d4b968f8 nfsd
R    415      1    415    415      0 0x42000000 ffffffffc5a9ea80 mountd
R    406      1    406    406      0 0x42010000 fffffe88c3d40020 snmpdx
R    390      1    390    390      0 0x4a014000 ffffffffc1f861a8 vold
R    381      1    381    381      0 0x42000000 fffffe88c3d456f8 sshd
R 15695    381    381    381      0 0x42010000 fffffe8946f77918 sshd
R 15696 15695    381    381    219 0x52010000 fffffe8ab1819730 sshd
R 15702 15696 15702 15702    219 0x4a014000 fffffe88d4b90568 bash
R   6927    381    381    381      0 0x42010000 ffffffffc9e748e8 sshd
R   6928   6927    381    381    159 0x52010000 fffffe8946f76048 sshd
R   6934   6928   6934   6934    159 0x4a014000 ffffffffc5a9ac78 bash
R    312      1    312    312      0 0x42000000 fffffe88dc9b3570 syslogd
R    306      1    306    306      1 0x42000000 fffffe88dc9b4e40 lockd
R    297      1    297    297      0 0x42000000 ffffffffc5a9c548 utmpd
R    270      1    270    270      0 0x42000000 ffffffffc9e75550 inetd
R    254      1    250    250      1 0x42000000 ffffffffc1f848d8 nfs4cbd
R    253      1    253    253      1 0x42000000 fffffe88c3d46360 statd
R    252      1    252    252      1 0x52000000 fffffe88d4b911d0 nfsmapid
R    247      1    247    247      1 0x42000000 fffffe88d4b94370 rpcbind
R    246      1    246    246      0 0x42010000 fffffe88c3d40c88 cron
R    225      1    225    225      0 0x42010000 fffffe88d4b9b368 xntpd
R    180      1    178    178      0 0x42000000 fffffe88d4b981c8 iscsid
R    147      1    147    147      0 0x42000000 fffffe88d4b97560 picld
R    143      1    143    143      1 0x42000000 fffffe88d4b9a700 kcfd
R    134      1    134    134      0 0x42000000 fffffe88c3d42558 syseventd
R    141      1    141    141      0 0x42000000 fffffe88d4b98e30 nscd
R     54      1     54     54      0 0x42000000 ffffffffc9e77a88 devfsadm
R     11      1     11     11      0 0x42000000 ffffffffc1f83c70 svc.configd
R      9      1      9      9      0 0x42000000 ffffffffc1f85540 svc.startd
R    286      9    286    286      0 0x4a004000 fffffe88dc9b7378 sh
R    261      9    261    261      0 0x4a014000 fffffe88d4b8f900 sac
R    305    261    261    261      0 0x4a014000 fffffe88d4b91e38 ttymon
R      5      0      0      0      0 0x00020001 ffffffffc1f89348 zpool-zbootDouble Fault could perhaps indicate that we have stack overflow in the kernel? Can I use mdb to dump all the currently-used-stack memory, and collect that data to see if there is a leak? I could also double the stacksize and see if the period between trouble also doubles.
Any other suggestions which may help in locating the troubles we are seeing?

SteveS,
Thanks for the reply. I have handed it off to the local support, and believe they have forward it to Oracle Japan. Possible, it goes through a lot of language translation, so it is a little like playing Telephone.
I was trying to decipher your ::cpuinfo -v information to see if I could determine if we were having this issue. But I am unsure what to look for in a non-healthy system.
This is the output I get
::cpuinfo -v
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
0 fffffffffbc29320 1f    1    0 -1   no    no t-3    fffffe8000005c60
(idle)
                  |    |
       RUNNING <--+    +--> PRI THREAD      PROC
         READY                60 fffffe80000b9c60 sched
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
1 ffffffffc3af2000 1f    1    0 -1   no    no t-3    fffffe80003bec60
(idle)
                  |    |
       RUNNING <--+    +--> PRI THREAD      PROC
         READY                60 fffffe800014fc60 sched
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
2 fffffffffbc310a0 1b    1    0 -1   no    no t-81   fffffe8000470c60
(idle)
                  |    |
       RUNNING <--+    +--> PRI THREAD      PROC
         READY                60 fffffe80001a3c60 sched
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
3 ffffffffc4270800 1f    0    0 -1   no    no t-123 fffffe80004cac60
(idle)
                  |
       RUNNING <--+
         READY
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
4 ffffffffc4270000 1f    0    0 -1   no    no t-77   fffffe8000561c60
(idle)
                  |
       RUNNING <--+
         READY
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
5 ffffffffc44be800 1f    1    0 -1   no    no t-0    fffffe80005a9c60
(idle)
                  |    |
       RUNNING <--+    +--> PRI THREAD      PROC
         READY                60 fffffe8000bbdc60 sched
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
6 ffffffffc44be000 1f    0    0 -1   no    no t-41   fffffe8000445c60
(idle)
                  |
       RUNNING <--+
         READY
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
7 ffffffffc4640000 1f    0    0 -1   no    no t-24   fffffe8000638c60
(idle)
                  |
       RUNNING <--+
         READY
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
8 ffffffffc4633800 1f    0    0 -1   no    no t-57   fffffe80006c9c60
(idle)
                  |
       RUNNING <--+
         READY
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
9 ffffffffc4633000 1f    0    0 -1   no    no t-23   fffffe8000739c60
(idle)
                  |
       RUNNING <--+
         READY
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
10 ffffffffc46ae800 1f    0    0 -1   no    no t-28   fffffe80007cac60
(idle)
                  |
       RUNNING <--+
         READY
      QUIESCED
        EXISTS
        ENABLE
ID ADDR        FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD      PROC
11 ffffffffc46ae000 1f    0    0 -1   no    no t-7    fffffe8000866c60
(idle)
                  |
       RUNNING <--+
         READY
      QUIESCED
        EXISTS
        ENABLE         As for "ps" we only have 42 procs, and threads the biggest process is "nfsd" (can use up to 1024, but hovers around 300). We are not hanging (or even considering the fork error) due to normal resource limits.
While waiting, I am poking around in the dump to see if we can find anything interesting. Last time, Telka managed to find out about the OpenOwner lock leaks, which was encouraging.

System Crash / Kernel Panic

My 21.5" iMac (Mid 2010) is crashing upon startup.
If anyone can help identify the cause, it would be most appreciated.
Some of the key lines on the screen are:
Panic(cpu 2 caller 0xffffff80002c268d): Kernel trap at0xfffff80005df60e, type 14=page fault, registers:
Debugger called; <panic>
Backtrace (CPU 2) Frame: Return Address
BSD process name corresponding to current thread:kernel_task
A picture of the screen is here:
http://imageshack.us/f/708/img2841p.jpg/

1. Shutdown the computer.
2. Put the disc in the DVD drive.
3. Start up the computer holding down the "C" key until you see the apple logo
4. When the computer boots, select the language.
5. Select Disk Utility from the Utilities menu.
6. Select your hard drive from the list on the left.
7. Click on the First Aid tab.
8. Click on Repair Disk and let that run.
9. Click on Repair Permisssions.
10. Reboot machine
This is may or may not fix it, it is just the first step in troubleshooting your problem.

10.6.4 Combo Update - Kernel Panic on 1st Gen Mac Pro with 8GB and ATI 4870

Hi,
I installed the 10.6.4 combo update last night and now my system constantly kernel panics. It was fine with 10.6.3 for months and never kernel panicked.
I have 4 x 2GB FB-Dimms and a ATI 4870 card.
The system is also only showing one display and I can force it to kernel panic by going to system preferences and selecting 'Detect Displays'.
Anyone got any suggestions before I reinstall back to 10.6.3?
Thanks
Paul

Hey guys. I have got a new Macbook Pro 13" model and I am getting kernel panics. I've been trying to partition the drive for Boot Camp and after I updated yesterday (to 10.6.4) i've been getting the kernel panic sign. Also, when I boot from my Snow Leopard disk to go into Disk Utility to repair the permissions (I opened Onyx and on the SMART check it said the permissions needed to be reset) I get a kernel panic and it crashes! So at the moment i've just backed up my work and I am panicking myself as I have no idea what to do from here.
Any help would be appreciated!

Kernel panics following wakeups using Leopard

I had been encountering routine system crashes (kernel panics) after waking my G5 from sleep mode. In an effort to isolate a possible cause, I changed USB hubs, disconnected external hard drives, and so on. What seems to have been the source (fingers crossed) of the panics was the D-Link DBT-120 Bluetooth dongle (USB). After removing that, I've had no further crashes (again, fingers crossed).
I'm curious if others have experienced the same or similar problems.

In another post I wrote
I have been in discussions with Apple Support for the last 6 weeks with ongoing kernel panic problems. We narrowed these down to LCC and it's accompanying files. LCC is LOgitech Control Centre which is installed to control the mouse gear wheel etc on the MX Revolution and others.
The Mac does one of two things.
In 10.4.10 and Leopard 10.5.1 the mouse constantly freezes on the screen, the keyboard still works and all apps can be quit and work saved. Checking activity monitor shows the Logitech software in red, all with problems. On logging out, the mac freezes. A forced restart with the poer button is the only way of restarting.
In Leopard 10.5.1 the Mac also constantly has Kernel Panics on wake up from periods of sleep. These can be just 2 minute periods or 2 hour periods, it's random.
If a Mac is woken from sleep and it enters a Kernel Panic, shortly afterwards a the fans rev to full throttle. This could potentially be a risk in a studio with several macs left on sleep for the night. Especially if someone caught the mouse on a Mac on the way out one night....would they get hot revving all night? Logitech should seriously look into this problem as it appears from all our tests that it is definately their software causing the problems.
We have tried upgrading to the latest 2.4 LCC software, still the kernel panics and mouse freezes continue.
If I remove the USB dongle before the computer sleeps it doesn't have kernel panics. However this is not practical and it still doesn't help the freezing issue.
Apple support have been fantastic in helping us with this problem, but the underlying cause lies with Logitech. Once again, we have a fantastic product and amateur software from Logitech.

Bizarre repeating Kernel Panic

About a year ago, my good old iMac began to exhibit a strange display error, Green (sometimes blueish, or any any color really, but primarily blue-green) gradient blocks started to pop-up everwhere. Finder windows, Menu Bars, Desktop, heck, coming out of sleep once the entire screen was taken over.
Anyway, if nothing was done about this, the system would Kernel Panic, and one would have to restart. At first i thought this to be one of the elusive mac viruses, so i bought norton antivirus, and ran the program. Well, halfway through, the machine kernel paniced. i tried booting it off of the CD, and while the system didn't kernal panic, the display error was very prevalent.
i reinstalled the OS, i reformatted the hard drive, i even took it to the Mac Genius thing, but infuriatingly, the one time i want it to kernel panic, it doesnt, so they said it's probably a logic board error. nothing got rid of the error for more than a week or two at best.
Eventually, furious, i bought a macbook. So while this isn't the most pressing thing in the world, it would really help if you could tell me what to do to fix it. Here's the panic.log file for one of the errors... i think they're mostly the same. i don't have a screen shot of the display problem, sorry!
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000002E88934E PC=0x000000000080EE14
Latest crash info for cpu 0:
Exception state (sv=0x2EAF1C80)
PC=0x0080EE14; MSR=0x00009030; DAR=0x2E88934E; DSISR=0x40000000; LR=0x0080F82C; R1=0x0CEE3AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008106C4 0x0080F82C 0x0080807C 0x007F7C74 0x002E7EE0 0x002E9DAC
0x0008C4B0 0x000291C0 0x000233AC 0x000AC02C 0x64617461
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x7ec000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45c000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x5e9000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x60d000
dependency: com.apple.NVDAResman(4.1.8)@0x623000
Proceeding back via exception chain:
Exception state (sv=0x2EAF1C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20E72500)
PC=0x9000B1E8; MSR=0x0200F030; DAR=0x04513A30; DSISR=0x40000000; LR=0x9000B13C; R1=0xBFFFE900; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.5.0: Sun Jan 22 10:38:46 PST 2006; root:xnu-792.6.61.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8384 0x000ABD00
Proceeding back via exception chain:
Exception state (sv=0x2EAF1C80)
PC=0x0080EE14; MSR=0x00009030; DAR=0x2E88934E; DSISR=0x40000000; LR=0x0080F82C; R1=0x0CEE3AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008106C4 0x0080F82C 0x0080807C 0x007F7C74 0x002E7EE0 0x002E9DAC
0x0008C4B0 0x000291C0 0x000233AC 0x000AC02C 0x64617461
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x7ec000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45c000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x5e9000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x60d000
dependency: com.apple.NVDAResman(4.1.8)@0x623000
Exception state (sv=0x20E72500)
PC=0x9000B1E8; MSR=0x0200F030; DAR=0x04513A30; DSISR=0x40000000; LR=0x9000B13C; R1=0xBFFFE900; XCP=0x00000030 (0xC00 - System call)
Kernel version:
is there anything i can do to save to computer?

Hello one:
Welcome to Apple discussions:
Flat statement - there are NO documented viruses (elusive or otherwise) that affect a Mac running OS X. I strongly suggest you dump the Norton AV software. While their AV software seems to run OK, Norton stuff caused OS X users (including me) serious problems in the past. The software manufacturer has dropped support for most Mac software.
Now then, to your issue.
I do not read kernel panics well. However, if you have reinstalled OS X, you have eliminated almost all software-related causes of kernel panics. That, of course, leaves hardware. I do not read crash logs well, unfortunately. I would, however, run the hardware checker that came with your Mac to see if it points to any problems. You can also check on the HD (unlikely cause, based on your post) by opening disk utility and highlighting the hD (not your files). At the bottom is something called S.M.A.R.T. If that says anything other than verified, you have a HD problem.
Barry

Kernel panic solution - My experience

I faced kernel panic during kernel update. Here is my experience in solving the issue:
http://cutecomputer.wordpress.com/2006/ … -solution/
I request Arch developers to take care of this issue which often raises. It is mostly related to update of kernel command line in grub/lilo.

Most important step people have to remember when updating latest 2.6 kernel: http://www.archlinux.org/news/

2010 mac mini kernel panics with kg os, mlb, ram, powersupply, etc what now?

Mac mini (Mid 2010)
Serial # DC*******6H
MAC MINI 2.4/2X1G/320/SD/AP/BT
AppleCare Protection Plan
Unit Received Date 08/26/13 05:19 PM
This is Rodney Watson. tch id(sc28f02f0b). Please contact me at********** I have no access to tsps. I have no contact information that successfully gets me feedback and I very much would love to get this machine back to its owner within two weeks if possible. I have a file of crash reports and other potentially useful data regarding this repair.
The initial issue with the system was that after a short time on a browser, the system would kernel panic, then the system would restart. I tried the quick fixes, resets, (updates are current for the user's volume) I tried a startup volume with a known good operating system, (OS X 10.8.3). I used known good ram, power supply, logic board, hard drive w fresh install of OS X 10.8.3. I still get the same behavior from thi sunit. It either boots to the desktop and crashes and restarts only to kernel panic and restart again, or it never gets to the desktop and repeatedly crashes/ restarts.
<Personal Information Edited by Host>

Hmmm, which exact Mini is it, a 2010 Mini should take 16 GB of RAM... but not just any RAM...
http://www.everymac.com/systems/apple/mac_mini/specs/mac-mini-core-2-duo-2.4-mid -2010-specs.html

Kernel Panics during system boot, and no kind of network connectivity

I've tried quite a lot of things here, so please read them all before you suggest something - and thanks for taking a look at my question (-:
I recently got my Mac Pro back from the AlaskaMacStore (not an actual apple retail store, and they aren't very good at that), having brought it in for loss of FW800. They sent it to Apple, and I received it back, supposedly with a new motherboard - and my FW800 working. However, it proceeded to kernel panic (complete visual system freeze, not greyscreenofdeath - oddly enough, iTunes would never stop playing during them) at least once a day after that.
Not wanting to deal with them again, I just used it like that and put up with it - but soon enough, I lost any sort of network connectivity as well. With AirPort connected to my Time Capsule's network (which worked fine on my Macbook Air and iPhone and various other devices), I was being told "...Self-Assigned IP address, and thus may not be able to connect to the internet...". Even connected directly via Ethernet to the Time Capsule, or directly via Ethernet to the cable modem, or directly via Ethernet to another Mac, or connected to another Mac's ad-hoc network, I could get absolutely no network communication going on of any sort.
This was too much for me, as all of my work requires frequent and heavy internet access, so I gave in and took it back to the local mac store equivalent - they charged me 100$, and kept it two days, just to tell me they 'couldn't reproduce the problem'. I took the Mac Pro to a friend's house, and went through the same tests - connected to his modem, with his Ethernet cords, and to his wireless and other macs. Same deal, no connection or indication of a networking being connected beyond that blasted 'self-assigned IP' in Network prefs.
Having no desire to be defrauded by the local fools again, I decided I didn't really have anything important on my internal hard drive, and decided to wipe the internals and re-install Leopard. My horrible luck continuing, I found my only Leopard disc to be cracked, prompting me to drive out and purchase a new one. Inserting this into my Mac Pro's drive, I found myself faced with yet another horrible problem.
During the boot to the Leopard DVD, the grey loading screen (with the apple logo and the spinner) simply froze with the spinner pointing left. I left it for a while, expecting this to be part of what I'd previously experienced with the slow boot-from-DVD on a Macintosh... but after 30 minutes of waiting, I got quite worried, and booted back into my normal OS by holding down Option and selecting my RAID.
Now, note this for later - it booted absolutely fine, and though I still had no network connectivity, the system had no problems. I changed the startup-disk to my RAID and then back to the Leopard DVD, naïvely thinking this would solve the problem, and ran into the same problem after restarting and booting to the Leopard DVD again.
Dismissing this as a optical drive problem (haven't had occasion to use optical media in nearly 3 years, don't really trust it in general), I booted the Mac Pro into Firewire Target Disk mode, and connected it to my Macbook Pro, and then booted the Macbook Pro from the installation DVD. Again, note carefully here - there was nothing wrong with the DVD itself, as the Macbook Pro had no trouble booting to the DVD.
I used Disk Utility to preform some planned modifications to the internal drives of my Mac Pro (erasing my previous inefficient RAID setup in favor of a new, faster (but less secure) RAID0 striped setup for my main two 1TB drives), and then proceeded to install a fresh Leopard onto the newly minted RAID. I usually cancel the 'disc checksum' that the Leopard DVD runs on itself, not really worrying about it, but in light of recent possible problems with the DVD, I went ahead and let it run - no problems, it completed and went straight into the normal install.
The install itself completed in a timely manner, and my Macbook Pro re-booted automatically, to the newly Leopard-ed RAIDed internals on the Mac Pro. It booted to the new install without a hitch, played the Leopard intro video, and continued to the setup cube. I opted to shut down (by hitting command-q and selecting the shut down option), so I could set it up on the Mac Pro instead.
Surprised was I, when I experienced the same grey loading screen freeze on the Mac Pro, booting to the newly clean install on the new RAID, that I had seen trying to boot to the Leopard disc. Worrying that my Leopard disc was, infact, corrupted in some way, I tried placing the Macbook Pro into firewire Target Disc Mode, and booting that drive over FW800 on the Mac Pro. Same freezing problem occurred.
Well, now, the only installation that HADN'T kernel panicked on boot was the old install, and that had been erased for the new RAID configuration, so I was left without a way to boot to a working install and test things from the Term. This left me with Single User Mode, which I immediately booted into.
Interestingly enough, there was no problem booting into Single User Mode - so I poked around a bit before mounting, and I had seemingly fine access to the entire filesystem of the new Leopard install, and nothing looked screwed up to my (albiet untrained) eye. After mounting and continuing the boot, it froze - but since this was verbose SUM, and not simple normal boot, I was able to see exactly where it froze: something about 'mDNSResponder starting', and then no input or output was accepted, leaving me assuming it had kernel panicked again.
To test this, I again attempted to boot from the Leopard DVD on the Mac Pro, this time in verbose startup mode, and watched it freeze up at exactly the same point. After a little googling, I found some suggestions to disable the launchd plist for mDNSResponder - I tried SUM again, and did so, then continued with the boot. This time, there was no output relating to mDNSResponder, so the launchd change had worked; however, it still froze - this time, right after three lines, first something along the lines of 'Login Window Application Starting', and then two lines printing Ethernet IDs of some sort. After those Ethernet related lines, it again froze.
What with the DNS and Ethernet bits showing up in the freezing, I was getting worried this was still tied into my NIC in some way, so I unplugged my Ethernet cords and tried the exact same boot again, and again disabled mDNSResponder. This time the only sensible thing before the freeze was the 'Login Window Application Starting' line, which seemed perfectly normal. I doubt there is/was anything wrong with that, so I'm assuming there's still some networking-related process freezing/panicking the computer, and it just doesn't happen to log in a visible way during startup.
Does anybody have any suggestion as to what such a process might be, and how I can at least pause or kill it from SUM, so I can at least finish booting the computer?
If I can't figure out a solution to this, I'll have to buy a new Mac Pro tomorrow morning... I have very, very pressing matters that can't wait for a new Mac Pro to ship, nor can they wait for me to ship this one to Apple and back (I live in Alaska, we have at least a weeks wait if nothing is seriously wrong when sending an Apple product in for repairs on our own), and nor can I wait 2 days for the local Apple store to tell me there's nothing wrong with it and then have to wait another week to, again, send it to Apple myself. I don't want to have to shell out for a new, expensive computer when there's a (most likely) perfectly good one sitting here... so any help would be MUCH appreciated.
If you've read this far, phew, you deserve a cookie. That was one... long... post.
(If you care, this post was cross-posted to my blog, at http://blog.elliottcable.name/posts/macpro_epicfail.xhtml)

Talk about bad luck.
The point at which the system "freezes" with the gray spinner (and just after the login window app starts) is right about the point the accelerated drivers should kick in for the video card.
So a couple things could be going on.
1) bad video card dragging down the bus
2) The system board is fubar - this I think is likely - issues with onboard ethernet, and whats seems to be video card related.
I would hazard to guess that the PCI-express bus has something wrong with it, ethernet and video live on the bus, SATA, and USB live in the southbridge.
So, looks like a trip to a certified apple dealer/repair center is next for your Mac Pro - probably for a new system board, again?
Something tells me that your system really didn't get to Apple for a new board.
You can verify by looking at the serial ID tag on the system board, note the rev and serial # before and after such repairs.

Memory issues - kernel panics / system freezes with 1Gb Memory Card

I've recently updated my PowerBook OS to 10.4.7 and now more recently 10.4.8.
Prior to this, i had been running a pair of pc2700 memory cards (1x1Gb + 1x 512Mb) bought from crucial technology on 10.3.9 with no problems.
During the upgrade, i experienced complete system lock ups and kernel panics. pulling the 1Gb card resolved the problem.
So i thought it could be duff memory (it happens). I ran hardware checker, both long and short tests, ran memchecker from single user and there was no reported errors although i was still getting crashes.
I returned the memory to crucial and they replaced it and then i went to reinstall memory in the pb.
Once reinstalled, problems re-emerged. Both System profiler and iStat pro show both memory sticks as ok. both are pc2700 DDR.
i tried just the 1 Gb stick in alternate memory slots. with the memory in the lower slot i was getting system freezes, in the top slot i was getting kernel panics.
I've pulled the 1Gb and reverted to 768Mb (512Mb lower (crucial)/ 256MB (apple) upper) and i'm back to normal.
Now what?
As my mac is getting on, i'd like to get as much RAM in it as i can, ideally the 1.5Gb /2Gb which it can support. I'd be suprised if it could be the memory stick being duff (2 duff in a row?), its not a faulty memory slot as system profiler is showing that its full.
Any suggestions? Anything to do with how 10.4.8 handles the memory addressing?
Any help would be appreciated.
PowerBook G4 1Ghz FW800 Mac OS X (10.4.8)

I've had that problem, too. I found out that it was one of my memory modules that were broken.
I'd say pop back in your other memory module, then get out your PowerBook DVD and stick it in Restart your PowerBook while holding down the Option Key on your keyboard until some buttons start to show up on your screen.
Select the Hardware Test one, then click the Arrow button. It'll boot into a utility and you can run a hardware test that includes checking your memory.
If any of your memory is bad, it'll show up like "**ERROR ERROR**" and give you a code.
After you've identified the hardware problem (hopefully just the RAM), then you can go to Crucial's website and fill out an RMA request to have the memory replaced. I'm pretty sure Crucial has a life-time warranty on their memory products.

A dozen+ Kernel Panics, suspect system issues - what to try?

Hello!
Well, in the last few weeks, my poor little Powerbook has lost its mind. I keep having Kernel panics for no apparent reason. Here's the story so far:
1. I upgraded to Leopard (archive/install) from Tiger, in November.
2. In early January, I had at least one kernel panic. Not sure what happened. By the middle of January, I had 3 or 4, and on (about) the 15th, I had three kernel panics in the span of an hour - and the lower ram card wasn't being recognized. I took it to the Apple store, where the tech said that it was the infamous "lower ram-slot issue" that plague my model Powerbook.
3. Once I got the powerbook back from the shop, it seemed to work quite well - fast, stable, panic-free. This week, however, I've had at least 6 or 7 kernel panics - at least 4 of them in the last 24 hours. A few of these weren't the usual "you need to restart your mac" window, but rather a long list of console-like text from the BSD subsystem itself
It seems to be related to the software - or perhaps Dashboard. Dashboard client has been running out of control this week - and started to go nuts about when the kernel panics started to occur. In fact, one of these "BSD" panics said that the dashboard client hung the computer. Thus, I moved all of my user (non-apple) widgets out of the library folder - effectively removing them from dashboard. This has prevented dashboard client from going nuts, but hasn't stopped the kenel panics. The ones that have occurred since seem to occur when using Safari or MS Word 2004, and one (another BSD panic) said that Window Server hung.
I've repaired permissions many times, used Disk Utility to verify the boot volume (it was OK), and zapped the PRAM and PMU - no luck.
I've had some other hardware and software issues:
First, Spotlight crashes when I attempt to search for something with a common name and have my 4 external hard drives attached... (One with Time Machine backups, one with other backups, and the rest with large volumes of video editing files). This issue probably isn't related to the kernel panic issue though, since it only occurs if I spotlight gets really bogged down - say, I search on "mac" and get 5000 returns...
Sometimes, if I have the power adapter plugged in and then boot up or wake the Mac, it sometimes won't recognize the adapter and thus run off battery. The solution? Unplug the adapter from the Mac and the wall, then plug both sides in. This occurs at least once a day, having become a much worse issue since sending it into Apple. This makes me think that I may have a issue with the power supply system in the Powerbook, and may be one of the causes of the panics. Again, zapping the PMU and PRAM, hasn't helped. Nor has deleting every power-related plist file.
The ram issue seems to have stopped, and I'm not sure the power issue could cause this - so I don't know what to do about this. It's happening a lot, but it's not exactly predictable - it would be difficult to reproduce for the Mac Genius, should I run to the Apple store. Since I suspect it's a software issue, I'm also not sure they can do anything about it. If Apple can't do anything about it, I plan on doing an Erase-install of Leopard, then carefully installing software - one thing at a time - to see if I can find the culprit. If worst comes to worst, I'll downgrade to Tiger...
So then, the questions, summed up are:
1. Do you have any idea what could be going on?
2. Can apple do anything about a software-related kernel panic issue?
3. If Apple can't fix it, and an erase-install won't work, when else can I try?
Sorry for the long post, and thanks a bunch for the help, I appreciate it.
-Dan

K, well i'll try to find the log on the backup clone I made - the Powerbook is currently in the Apple store for diagnostics. Hopefully, then can figure out what the deal is, but it will likely require an archive/install.
When I was there, he opened one of the logs in console - and it showed literally thousands of errors - all from "kernel". Wow, i have no idea what happened. He said that it may be bit-rot on the part of some of my applications, but there's probably not much they can do if it's not a hardware problem. sigh
Anyway, I'll look for the log on the backup volume when I get a chance. Thanks, I suppose you're right about you being forced to guess without the log. Didn't think about that... O:-)

Kernel panic after system update - can't boot :(

Hi
I've applied some pending updates to the system while restarting my MBP (I'm not sure, but it probably has contained the update from 10.6.3 to 10.6.4) but now it won't boot - I get a kernel panic.
When I boot instead using an external USB drive with a 10.6.3 installation on it, I get the message about the panic (below).
Any ideas how to solve this would be VERY MUCH appreciated.
Thanks!
Fri Aug 13 03:23:05 2010
panic(cpu 1 caller 0x4f9be4): "IOBluetoothHCIController::_RESERVEDIOBluetoothHCIController59 called."@/SourceCache/xnu/xnu-1504.3.12/libkern/c++/OSMetaClass.cpp:906
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x82cd3a98 : 0x21b449 (0x5ce420 0x82cd3acc 0x2238a5 0x0)
0x82cd3ae8 : 0x4f9be4 (0x5cef90 0x814b0de8 0x814b0de8 0x3b)
0x82cd3b08 : 0x81486ba4 (0x814bc114 0x3b 0xcad3540 0x0)
0x82cd3b28 : 0x82f21d7f (0xc1c1e00 0xc9ff194 0x2 0x82ec3c03)
0x82cd3b78 : 0x82f22b6a (0xc9ff100 0x0 0x0 0xc9d6f00)
0x82cd3dc8 : 0x82ec31dc (0xc9ff100 0xc9fc300 0x82cd3df8 0x4faec3)
0x82cd3df8 : 0x82f20dc0 (0xc9ff100 0xc9fc300 0x82cd3e28 0xcacc780)
0x82cd3e18 : 0x5382aa (0xc9ff100 0xc9fc300 0x1 0x4fb2b4)
0x82cd3e78 : 0x5364df (0xc9fc300 0xc9ff100 0xcaccb80 0xca660e0)
0x82cd3f28 : 0x536a70 (0xc9fc300 0xcac9900 0x0 0x50aea4)
0x82cd3f78 : 0x53871f (0xc9fc300 0x8 0x82cd3fac 0x1)
0x82cd3fc8 : 0x29e6cc (0xcb41210 0x0 0x29e6db 0xc62f000)
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.IOBluetoothSCOAudioDriver(2.3.7f1)@0x82f1f000->0x82f25fff
dependency: com.apple.iokit.IOAudioFamily(1.7.6fc2)@0x82ebf000
dependency: com.apple.iokit.IOBluetoothFamily(2.3.1f4)@0x81480000
com.apple.iokit.IOAudioFamily(1.7.6fc2)@0x82ebf000->0x82ed6fff
dependency: com.apple.kext.OSvKernDSPLib(1.3)@0x8147c000
com.apple.iokit.IOBluetoothFamily(2.3.1f4)@0x81480000->0x814bcfff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10F569
Kernel version:
Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386
System model name: MacBookPro5,1

Kappy, I have various bluetooth devices (headset, wireless wacom tablet, etc) that I use from time to time, but the kernel panic happens very early in the boot process.
When I tried booting in safe mode (holding shift), I got the panic much sooner, but of a different type now:
Fri Aug 13 04:35:52 2010
panic(cpu 1 caller 0x474607): "Process 1 exec of /sbin/launchd failed, errno 2\n"@/SourceCache/xnu/xnu-1504.3.12/bsd/kern/kern_exec.c:3146
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x7ab83e48 : 0x21b449 (0x5ce420 0x7ab83e7c 0x2238a5 0x0)
0x7ab83e98 : 0x474607 (0x5c06ac 0x831b68 0x2 0x0)
0x7ab83ef8 : 0x45e836 (0x5a22d20 0x1fe 0x575ca80 0x80000001)
0x7ab83f38 : 0x484da2 (0x57fdb7c 0x73aa5000 0x7ab83f88 0x7ab83f94)
0x7ab83f68 : 0x219044 (0x57fdb7c 0xffffff7f 0x0 0x575eb7c)
0x7ab83fa8 : 0x2a7a07 (0xffffffff 0x1 0x22f250 0x575eb7c)
0x7ab83fc8 : 0x29e8a6 (0x0 0x0 0x29e6db 0x524c0e0)
BSD process name corresponding to current thread: init
Mac OS version:
Not yet set
Kernel version:
Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386
System model name: MacBookPro5,1

Duel System Adapter + MacBook Pro = Kernel Panic?

I was on set for a P2 shoot as the "P2 Dumper" a few days ago. Cards where all ranges of sizes (4GB to 32GB) offloaded to my MacBook Pro via a Duel Systems Adapter. The MBP was purchased brand new on Sunday (2.5 Ghz 15"; so 10.5.2 & QT 7.4.1 were pre-installed). I installed the Panasonic P2 Mac utilities (P2PCCard Install, P2 Formatter, etc) as well as P2CMS after I installed FCS 2 and updated to FCP 6.0.2.
Now, I'd read that the Duel System Adapter usually required a system restart before you could typically read the card. What I didn't expect was the kernel panic I kept experiencing whenever I inserted a P2 card into the adapter after a period of inactivity.
What I mean to say is, when offloading one card after another (usually in the span of 20 minutes), I never got a kernel panic. But when I had to start the process from scratch - meaning I hadn't offloaded a card in 30+ minutes - inserting a card would guarantee a kernel panic.
This is with the adapter continually plugged in. Was that my mistake? Is it required to eject the adaptor when done with a series of cards, then reinsert it (and restart) when beginning the offloading process again?
I'm guessing this is just me overlooking an understood aspect of the workflow, rather than me bumping into some brand new issue...

Hey Hanumang,
I too am having kernel panics using the latest (Penryn, Feb refresh) Macbook Pro and a duel system adapter. My kernel panics have been occuring during ingest/export when using P2CMS. Here is my set up:
Penryn MBP
OSX 10.5.2
Quicktime 7.4.5
FCP 5.1.4
P2CMS 1.1.9 (latest)
I have all the necessary drivers (no additional drivers are needed with Leopard and the Duel Adapter).
My kernel panics are happening when I am ingesting/exporting using P2CMS after about 1gb of transfer. Here is my exact workflow:
Shoot 720/24pn on an HVX to an 8gb card.
Write protect 8gb card.
While off, insert Duel Adapter to MBP.
Boot MBP and insert P2 card into Duel Adapter, P2 card mounts fine.
Launch P2CMS
Select P2 card as the source
Select all clips -> right click -> export to MBP hard drive.
After about 1gb of transfer, I get a kernel panic, 5 times out of 5.
Notes: No issues with the Duel Adapter when using a drag and drop method. No issues using above workflow using P2CMS and using the HVX and firewire to mount P2 cards. I only get kernel panics when using the Duel Adapter and P2CMS to ingest footage.

Kernel panic - hard drive or corrupt journal system?

Hi,
My powerbook G4 shut down today with a kernel panic and now won't boot up (giving a kernel panic error after reaching the gray screen). The computer has been working fine, though the battery has run down, with the exception of not shutting down properly (I would have to power off manually). I tried various things to fix this (repair permissions, check hard drive, checking logs, etc.), but all those checked out and I could never get it figured out. I have been leaving the computer running because of this and it has been working fine. It is a stock G4 with no peripherals, except for a 1 GB RAM upgrade. The RAM was installed two years ago and tested strenuously with memtest with no issues.
I did have my hard drive near full, as I didn't realize that this could case severe issues. It's probably too full to do a clean Archive and Install. My fault.
I have reset my PMU/PRAM, but the computer won't boot up in safe mode or single-user mode. I get the following message at the end of single-user mode:
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007: root:xnu-792.24.17~1/RELEASE_PPC
panic: We are hanging here ...
Unfortunately, I do not have my backup disks with me right now, as I recently moved (I will have them in a couple weeks).
There's some data on the computer it would be nice to pull off, but not absolutely essential. So my question is: Does this sound like a hard drive problem or a journal system/file system problem or something else? I hear no strange noises from the drive (the fan is a little noisy, though). What can I do at this point while I wait for my discs to arrive from across country?
If this is a file problem, I have heard these are difficult to fix or even deal with in terms of data recovery, since the disk won't mount even in firewire target mode. Should I invest in a firewire external drive in order to create a bootable second drive? Purchase DiskWarrior? Create a bootable Linux CD? Any help would be appreciated!

darksurtur:
If you have the original HDD with which the computer was bought you likely have a failed HDD and should have it replaced with a newer, faster and large capacity HDD. The average life of an internal HDD is 3 to 5 years, and although it may not suddenly stop functioning after that performance gradually decreases until the drive fails completely.
A too full drive can cause serious directory corruption which can in turn lead to data corruption and possible loss, and eventually a crash. You should maintain a minimum of 15% to total disk capacity (5 GB minimum on HDDs of 40 GB or less) as contiguous free space to allow for swap files and directory expansion.
You should always maintain a current backup of everything you do not wish to lose as even a new HDD can fail suddenly. Using an external firewire drive and making a bootable clone using a utility like SuperDuper or Carbon Copy Cloner is an excellent way to accomplish this. Dr. Smoke's FAQ Backup and Recovery has excellent tips on backup strategies.
Please do post back if you have further questions or comments.
cornelius

Kernel panic after full system restore

Yesterday I noticed that my computer was quite slow. Seeing as how the hd has never been formatted since I have bought the computer in 2006 I thought the drive was badly fragmented. Since there are no free defrag solutions available for mac, I thought I would just format the drive and do a system restore using time machine. I did a full format with 1 pass of zeros then did a system restore. After the restore when the computer rebooted, I got a kernel panic. The kernel panic mentioned something along the lines of "Version mis-match between Kernel and CPU". I then chose to restore to an earlier backup but that yielded the same results.
I have done a lot of googling and most of the solutions to this problem indicate that the restore is being initiated from a Leopard install disc rather than a Snow Leopard install disc. I am using a snow leopard disc.
In the end, I did get my system working by installing snow leopard over top of itself then applying the latest combo update. The reason for this post is so I can hopefully find out why I got the kernel panic. This incident had cost me a lot of time and if I cannot rely on time machine as a backup solution then there is really no point in using it.
Thanks.

eradicator006 wrote:
Yesterday I noticed that my computer was quite slow. Seeing as how the hd has never been formatted since I have bought the computer in 2006 I thought the drive was badly fragmented.
Doubtful. See: [About disk optimization with Mac OS X|http://support.apple.com/kb/HT1375].
In the end, I did get my system working by installing snow leopard over top of itself then applying the latest combo update. The reason for this post is so I can hopefully find out why I got the kernel panic. This incident had cost me a lot of time and if I cannot rely on time machine as a backup solution then there is really no point in using it.
Something in your installation of OSX was probably corrupted, damaged, or missing, and Time Machine backed up the corruption (as would any backup utility). So when you restored, you brought the problem back.
That's likely also the reason your Mac was running "quite slow."

System facing kernel panic....

Similar Messages

Maybe you are looking for