Previous 1 2 Next 18 Replies Latest reply: Jul 26, 2011 5:55 PM by babowa
babowa Level 7 (29,975 points)

Twice in two days - running AHT right now; but in the meantime, copying the last panic report in case someone has a clue:


Interval Since Last Panic Report:  15860 sec

Panics Since Last Report:          1

Anonymous UUID:                    B5EC379A-F445-40A6-86B9-0F81E25D3F68


Sat Jul 23 21:07:01 2011

panic(cpu 1 caller 0xffffff80002c268d): Kernel trap at 0xffffff7f814d392d, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0x000000002eeb0676, CR3: 0x0000000000100000, CR4: 0x0000000000000660

RAX: 0x0000000000000001, RBX: 0xffffff800ce7e6c8, RCX: 0x000000000000000a, RDX: 0x0000000000000002

RSP: 0xffffff808e0e3c80, RBP: 0xffffff808e0e3cc0, RSI: 0x0000000000000a62, RDI: 0x0000000000000375

R8:  0x000000000000000d, R9:  0x0000000000000000, R10: 0x000000007e01d034, R11: 0x0000000000000064

R12: 0x0000000000000001, R13: 0x0000000000000001, R14: 0xffffff800ce7e6ec, R15: 0xffffff800ce7e600

RFL: 0x0000000000010206, RIP: 0xffffff7f814d392d, CS:  0x0000000000000008, SS:  0x0000000000000010

CR2: 0x000000002eeb0676, Error code: 0x0000000000000002, Faulting CPU: 0x1


Backtrace (CPU 1), Frame : Return Address

0xffffff808e0e3940 : 0xffffff8000220702

0xffffff808e0e39c0 : 0xffffff80002c268d

0xffffff808e0e3b60 : 0xffffff80002d7a3d

0xffffff808e0e3b80 : 0xffffff7f814d392d

0xffffff808e0e3cc0 : 0xffffff7f814d55e0

0xffffff808e0e3d10 : 0xffffff7f814a9704

0xffffff808e0e3de0 : 0xffffff7f814fb9bf

0xffffff808e0e3e40 : 0xffffff7f814fff5f

0xffffff808e0e3ec0 : 0xffffff7f814784d8

0xffffff808e0e3ef0 : 0xffffff8000639536

0xffffff808e0e3f30 : 0xffffff80006382b0

0xffffff808e0e3f70 : 0xffffff8000638154

0xffffff808e0e3fb0 : 0xffffff8000820057

      Kernel Extensions in backtrace:
[E735671D-DA91-3B74-92D1-339766E0D0C D]@0xffffff7f81468000->0xffffff7f81647fff

            dependency:[95ABB490-3AB5-3D5E-9C21-67089A9AE6A1]@0xffff ff7f8083e000

            dependency:[78A58272-2170-3068-9C63-88301C99C406]@0xf fffff7f81430000

            dependency:[59A00F6B-3710-3E07-9921-70C45782FF8C]@0 xffffff7f80f8b000


BSD process name corresponding to current thread: kernel_task


Mac OS version:



Kernel version:

Darwin Kernel Version 11.0.0: Sat Jun 18 12:56:35 PDT 2011; root:xnu-1699.22.73~1/RELEASE_X86_64

Kernel UUID: 24CC17EB-30B0-3F6C-907F-1A9B2057AF78

System model name: MacBook5,2 (Mac-F22788AA)


System uptime in nanoseconds: 77749685704

last loaded kext at 13682925243:    1.9.4d0 (addr 0xffffff7f81d10000, size 28672)

loaded kexts:    1.9.4d0    3.0    3.5.9    1.0.24    1.0.2d2    7.0.2    2.1.1f11    100.12.40    1.59    3.0.1d2    1.0.0d1    7.0.0    1.2.0    4.7.0b2    1.5.1    3.0.8    170.1.9    220.8    220.8    220.8    309    1.1.0    1.0.0d1    1.0.0d1    32    3.0.0    2.0.0    500.20.6    4.8.6    2.1.8    4.4.0    2.0.17    4.4.0    4.4.0    1.5.0    1.4    1.6    161.0.0    1.4    1.7    1.4    1.5    166.0.0    3.0.30    1    166.0.0    1.0    2.1.1f11    2.1.1f11    7.0.2    7.0.2    2.2.3    80.0    2.5f17    10.0.5    1.0.0d22    1.0.0d5    1.8.3fc11    1.3    2.1.1f11    2.1.1f11    3.1.1d2    4.7.0b2    1.0.10d0    3.0.8    1.0.3    2.3    2.3    4.4.0    13    2.5f17    2.5f17    2.5f17    4.4.0    3.9.0    3.0.0    1.6    1.6    1.7    403    2.0.0    3.0.0    400.40    4.4.3    2.0.6    4.4.0    2.0    4.4.0    2.2.9    1.5.0    1.7.0    1.1    165    1.0.0d1    7    326    1.7    28.18    1.4    2.6.5    1.4

System Profile:

Model: MacBook5,2, BootROM MB52.0088.B05, 2 processors, Intel Core 2 Duo, 2 GHz, 4 GB, SMC 1.38f5

Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB

Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F1600000000, 0x4E4C38323536343231323037462D4435334D

Memory Module: BANK 1/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F1600000000, 0x4E4C38323536343231323037462D4435334D

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (

Bluetooth: Version 2.5.0f17, 2 service, 12 devices, 1 incoming serial ports

Network Service: AirPort, AirPort, en1

Serial ATA Device: ST95005620AS, 500.11 GB

Serial ATA Device: HL-DT-ST DVDRW  GS22N

USB Device: Built-in iSight, apple_vendor_id, 0x8501, 0x24400000 / 2

USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0229, 0x04600000 / 3

USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x04500000 / 2

USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000 / 2

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0x06110000 / 5




As requested: 10223/84299

MacBook, Mac OS X (10.6.7), early 2009 4 GB RAM
  • Graham Perrin Level 2 (255 points)



    For starters, the four (wrapped) lines below Kernel Extensions in backtrace


    Take a Console view of all messages, of system.log, of kernel.log from around the time of the panic. From the logs, and from your recollection of what preceded the panic, can you think of anything significant network-related?


    If the date/time stamp in the .panic file is later than the time of the panic, it's probably because the data is written to NVRAM at panic time — not written to disk until after the computer is started.





    Side note (off-topic)


    Before I forget … if immediately following a panic Recovery OS is used, with various areas that are read-only, I wonder whether data relating to a panic may be lost from NVRAM. I should spin that question into a separate topic.




    Update your profile to show the more modern operating system etc.. Easily forgotten, I did the same

  • babowa Level 7 (29,975 points)

    Thanks -


    Take a Console view of all messages, of system.log, of kernel.log from around the time of the panic. From the logs, and from your recollection of what preceded the panic, can you think of anything significant network-related?


    This kernel panic was on startup (boot up) - nothing preceded it because it was off (no recollection necessary). Not sure what you mean with Network? I have a wireless router, but other than that, no network. Running Rember right now, so it may take an entire day before I can access any log on the Macbook.


    If the date/time stamp in the .panic file is later than the time of the panic, it's probably because the data is written to NVRAM at panic time — not written to disk until after the computer is started.


    Not sure I understand that one - shut down computer (while it was working properly and no sign of anything wrong during shutdown) one evening. Hit power button next evening - met with black curtain/restart message immediately after desktop appears.


    And yes, will update (once I decide if I am going to keep Lion running on this machine)

  • Graham Perrin Level 2 (255 points)

    Thinking more broadly, assuming that all things listed in the panic report are more thoroughly tested than third party software, a long shot: a Google search for panic +"USB to Serial-ATA bridge" Iomega finds two other reports of panics.


    One of those topics is from a user of something less than Lion. This post helped the opening poster to identify possible issues with third party software, but no suggestion of Iomega in that particular post.


    The other topic is more thought-provoking: Kernel Panic in Lion, where some people find use of Wi-Fi to be contributory to the problem.


    Still, assuming that testing of stuff was thorough, I'd like to rule out a few things.


    Do you have any USB-attached devices?


    Do you use any third party sensing software, such as iStat Menus or Little Snitch? Anything that might be monitoring network traffic or disk input/output?




  • babowa Level 7 (29,975 points)

    Do you have any USB-attached devices?


    No (rather, yes, I do, but they are only occasionally attached when I actually need them)


    Do you use any third party sensing software, such as iStat Menus or Little Snitch? Anything that might be monitoring network traffic or disk input/output?




    Any third party software on it has been around for some time and hasn't presented a problem - and, there is very little of it because this is not my "work" machine - it's my play machine. I do have the full suite of iLife, Aperture, FCE, and any other photo/movie related app on there, but that's about it.


    By the way, do I have to run Rember in the full 255 pass mode? Judging from what it's done in the past 3 hours, it looks like that could take a week... AHT (extended) reported nothing.

  • Graham Perrin Level 2 (255 points)

    Rember? No experience with that, sorry.


    Concerning possible causes of the panic: in at least one of the other topics where I gave the long shots, it seems that the shots were too long.


    If this does turn out to be an unexpected issue involving Wi-Fi, can you work instead with a wired connection (with Wi-Fi switched off in Mac OS) pending further investigation?

  • babowa Level 7 (29,975 points)

    Baltwo suggested that in addition to AHT, one needs to run Rember to definitively rule out (or in?) RAM problems.


    Yes, I could run it wired, but not really where I usually use it because that would involve a 50 ft ethernet cable snaking through my house..... and that is what I usually do with it: peruse the discussion forums (wirelessly). Again, there was no problem (wirelessly or otherwise) when I was running SL


    I think for now, I'll wait for Rember to finish (can't use it while that is running anyway) - may cut it off after a reasonable number of passes though. So far, it finished 3 and every entry shows "ok".

  • baltwo Level 9 (62,215 points)

    Rember is a GUI front end for memtest, which provides more detailed testing of RAM than available w/AHT.

  • baltwo Level 9 (62,215 points)

    Since the first item mentioned in Kernel Extensions in backtrace: is, I strongly suspect that the wireless router is what's mucking things up. Hook the MB directly to the internet, after running Rember, and see if the KPs stop.

  • babowa Level 7 (29,975 points)

    I will try it wired - once the Macbook is usable again - I'm going to cut it off shortly I think; it's run 6 passes now and every entry says "ok".


    But, I'm still convinced Lion is causing this because I've never had that problem with SL (with the same workflow) - the KP's started with Lion.

  • baltwo Level 9 (62,215 points)

    IMO, you should wait until Rember finishes. Use the iMac while it's doing its stuff. If the RAM passes all tests, then you can rule it out.

  • babowa Level 7 (29,975 points)

    Arrgghh - too late. I had just cut it off after 6 passes; I did the math: at the rate it was going (6 passes in 9 hours), it would take 10 days or more  (days, not hours) - that sounded too unrealistic to me, so I stopped it...... sorry. If below doesn't help, I'll run it again.


    By the way, you (and Graham) might be right on the money with the wireless because I've seen several threads now with Lion KP's and possibly Airport related, so the next thing to try will be to use it wired for a couple of days and see what happens.

  • baltwo Level 9 (62,215 points)

    Don't know why it's so slow on your MB, but when I ran it a year ago on my iMac w/12 GB RAM, it finished in less than a couple of hours. Anyway, try it wired and see if the KPs go away.

  • Graham Perrin Level 2 (255 points)

    Opening poster babowa has a MacBook5,2, I have a MacBookPro5,2. Both 2009 models according to MacTracker


    For many users of Apple computers that are not limited by EFI32, a most signifant difference between Snow Leopard and Lion will be:


    • default to 32-bit kernel extensions in Snow Leopard
    • default to 64-bit kernel and extensions in 10.7 (Build 11A511).


    Defocusing for a moment from the detail of this particular panic, let's assume that Apple has honed many things for the 64-bit default on the broader range of hardware. Maybe the honing is imperfect for MacBook5,2 and some other models, maybe imperfect for some classes of network hardware in those models.


    Back to babowa. Please start with the 32-bit kernel, see whether the panic is reproducible.


    Before changing the startup mode, please also:


    1. reset PRAM and NVRAM
    2. use the startup manager to ensure that the required volume is selected in boot options; do this because step (1) will lose your startup volume preference.


    References (not the best, but the nearest I can find at the moment)


    Mac OS X v10.6: Starting up with the 32-bit or 64-bit kernel — not updated for 10.7, so to draw Apple's attention consider giving a low rating (not helpful … or something less harsh, depending on your mood — the article probably is reasonably helpful in these early days of 10.7)


    Resetting your Mac's PRAM and NVRAM


    EFI and SMC firmware updates for Intel-based Macs


    Startup Manager: How to select a startup volume


    I recall at least one kernel panic at startup that involved multiple workarounds, only one of which was a reset.

  • babowa Level 7 (29,975 points)

    Just did a PRAM reset. Followed by a KP upon startup. Followed by another KP and a third one. After the third one - and I could not even get far enough to get/copy the panic report, but I remember the second one said something about Hardware - now I cannot get past the white screen with 3 beeps (with the LED flashing in unison) which appear to mean "no good banks".



    I'm guessing that means repair time?

Previous 1 2 Next