Previous 1 22 23 24 25 26 Next 386 Replies Latest reply: May 11, 2007 7:54 AM by Talmage Cooley Go to original post
  • dsavage Level 1 Level 1 (5 points)
    OK. Its been over 15 days an not a single KP on any of my 3 MacBooks. (YEA!!)

    What changed? I turned off the NetGear 108G and bought a Linksys 54G. Nothing else changed, not the auth, not the key, only went to a "pure" 54G

    I seriouly dont think its anything to do with the vender - its clearly a bug in the Apple Driver dealing with pre-N wireless signals.

    Come on Apple = Fix the driver bug already!!!



    MacBook Pro   Mac OS X (10.4.7)   pre-N 108G
  • Chris Pf Level 1 Level 1 (0 points)
    What changed? I turned off the NetGear 108G and
    bought a Linksys 54G. Nothing else changed, not the
    auth, not the key, only went to a "pure" 54G

    I seriouly dont think its anything to do with the
    vender - its clearly a bug in the Apple Driver
    dealing with pre-N wireless signals.

    Come on Apple = Fix the driver bug already!!!



    I'm glad to here that worked for you. Although, I have a Linksys WRT54G ver. 7, bought in Bangkok, around June right after I bringing my (week 19) MPB 17" home. Didn't start having KP's till one month later. I took the mpb back to the store where I bought it and they ran a hardware test resulting in finding a small error on the HD. They repaired that and reinstalled the OSX 10.4.6 That night it KPed again. The store sent it to the service center where they couldn't dup the event and sent it back to me. Again, the evening I get it back, KP twice! After updating to OSX 10.4.7, I still KP nearly every time I go wireless. Sometimes it takes 2 - 4 hours, others it happens in less than 15 minutes!

    They sent word to the Main Apple store for Asia in Singapore. I'm now waiting their prognosis. In the meanwhile I've been collecting info to show from these forums and other sources, i.e. http://macosg.com/index.php, to strengthen my case.

    I'll be travelling to the States in about two weeks and plan to visit an Apple Store or Genius bar there to see if I can expedite the process of ordering a new MLB or whatever it takes to fix this. It's a shame that such a fine piece of machinery, that comes at a primium cost, does not do what it's intended to do. The main reason I bought the MacBook in the first place was for the mobility that comes from going wireless!

    Enroute to my destination, I'll have ample time to experiment with different Access Points to see if that makes any difference.

    Here's a look at my latest KP that occurred while chatting with my daughter (she on her MPB 13" in LA, that hasn't had a single KP - btw).

    We really need to keep this topic alive till Apple gets the fix out - once and for all!

    Chris Pf

    panic.log:

    Description: Panic (system crashes) log
    Size: 16.56 KB
    Last Modified: 9/15/06 11:12 PM
    Location: /Library/Logs/panic.log
    Recent Contents: ...
    dependency: com.apple.iokit.IOPCIFamily(2.0)@0x566000
    dependency: com.apple.iokit.IO80211Family(112.1)@0x917000

    Kernel version:
    Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


    *******

    Sun Sep 10 08:37:07 2006
    panic(cpu 0 caller 0x0019CADF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0x04008019, CR3: 0x00d5e000, CR4: 0x000006e0
    EAX: 0x04008001, EBX: 0x03bab500, ECX: 0x03a70568, EDX: 0x03bab500
    ESP: 0x04008019, EBP: 0x24d63d68, ESI: 0x03ba4144, EDI: 0x03b7e56c
    EFL: 0x00010206, EIP: 0x003a11c8, CS: 0x00000008, DS: 0x36a90010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x24d63c20 : 0x128b5e (0x3bc46c 0x24d63c44 0x131bbc 0x0)
    0x24d63c60 : 0x19cadf (0x3c18e4 0x0 0xe 0x3c169c)
    0x24d63d10 : 0x197c7d (0x24d63d24 0x24d63d68 0x3a11c8 0x24d60048)
    0x24d63d1c : 0x3a11c8 (0x24d60048 0x15d0010 0x35c0010 0x36a90010)
    0x24d63d68 : 0x187952 (0x3bab500 0x3b94198 0x34 0x24d63da8)
    0x24d63d88 : 0x18a7e7 (0x3ba4138 0x1 0xbfe00000 0x0)
    0x24d63dd8 : 0x12b389 (0x3b94198 0x3b7e56c 0x0 0x0)
    0x24d63e18 : 0x124902 (0x3b94100 0x0 0x34 0x24d63efc)
    0x24d63f28 : 0x193034 (0x24d63f54 0x0 0x0 0x0)
    0x24d63fd8 : 0x19814b (0x3a707e0 0x3a707e0 0x3bab500 0x4008019) No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbfffe598

    Kernel version:
    Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


    *******

    Wed Sep 13 19:17:28 2006
    panic(cpu 0 caller 0x0019CADF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0xc306b323, CR3: 0x00d5e000, CR4: 0x000006e0
    EAX: 0xc306b322, EBX: 0x00000014, ECX: 0x24fabc8c, EDX: 0x00000014
    ESP: 0xc306b323, EBP: 0x24fabad4, ESI: 0x03fd8604, EDI: 0x03fd867c
    EFL: 0x00010286, EIP: 0x0093e23d, CS: 0x00000008, DS: 0x24fa0010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x24fab954 : 0x128b5e (0x3bc46c 0x24fab978 0x131bbc 0x0)
    0x24fab994 : 0x19cadf (0x3c18e4 0x0 0xe 0x3c169c)
    0x24faba44 : 0x197c7d (0x24faba58 0x24fabad4 0x93e23d 0x48)
    0x24faba50 : 0x93e23d (0x48 0x10 0x10 0x24fa0010)
    0x24fabad4 : 0x93c303 (0x3fd867c 0x36bb1843 0x8 0x64)
    0x24fabb24 : 0x931cb9 (0x3be3804 0x24fabc8c 0x36bb1800 0x50)
    0x24fabb84 : 0x942855 (0x393646c 0x24fabc8c 0x36bb1800 0x50)
    0x24fabce4 : 0x952bd9 (0x393646c 0x36c47e00 0x3df7404 0x50)
    0x24fabd34 : 0x9439a5 (0x393646c 0x36c47e00 0x3df7404 0x50)
    0x24fabe24 : 0x95386a (0x393646c 0x36c47e00 0x3df7404 0x3d)
    0x24fabf14 : 0x38dd6d (0x393629c 0x3a8e880 0x1 0x3bbce58)
    0x24fabf64 : 0x38cf19 (0x3a8e880 0x135d18 0x0 0x3bbce58)
    0x24fabf94 : 0x38cc3d (0x3a92000 0x3a92000 0x77 0x1)
    0x24fabfd4 : 0x197b19 (0x3a92000 0x0 0x3bbd0d0 0x14) Backtrace terminated-invalid frame pointer 0x0
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.AirPortAtheros5424(104.1)@0x930000
    dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x698000
    dependency: com.apple.iokit.IOPCIFamily(2.0)@0x566000
    dependency: com.apple.iokit.IO80211Family(112.1)@0x917000

    Kernel version:
    Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


    *******

    Fri Sep 15 23:12:51 2006
    panic(cpu 0 caller 0x0019CADF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0x3d746c62, CR3: 0x00d5e000, CR4: 0x000006e0
    EAX: 0x3d746c61, EBX: 0x00000014, ECX: 0x24f0bc8c, EDX: 0x00000014
    ESP: 0x3d746c62, EBP: 0x24f0bad4, ESI: 0x042b5a04, EDI: 0x042b5a7c
    EFL: 0x00010202, EIP: 0x0093e23d, CS: 0x00000008, DS: 0x24f00010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x24f0b954 : 0x128b5e (0x3bc46c 0x24f0b978 0x131bbc 0x0)
    0x24f0b994 : 0x19cadf (0x3c18e4 0x0 0xe 0x3c169c)
    0x24f0ba44 : 0x197c7d (0x24f0ba58 0x24f0bad4 0x93e23d 0x500048)
    0x24f0ba50 : 0x93e23d (0x500048 0x36c0010 0x37f0010 0x24f00010)
    0x24f0bad4 : 0x93c303 (0x42b5a7c 0x36c5f843 0x8 0x1be)
    0x24f0bb24 : 0x931cb9 (0x3be6804 0x24f0bc8c 0x36c5f800 0x50)
    0x24f0bb84 : 0x942855 (0x393a46c 0x24f0bc8c 0x36c5f800 0x50)
    0x24f0bce4 : 0x952bd9 (0x393a46c 0x36c62000 0x3dd4004 0x50)
    0x24f0bd34 : 0x9439a5 (0x393a46c 0x36c62000 0x3dd4004 0x50)
    0x24f0be24 : 0x95386a (0x393a46c 0x36c62000 0x3dd4004 0x31)
    0x24f0bf14 : 0x38dd6d (0x393a29c 0x3a92880 0x1 0x3bc0ad0)
    0x24f0bf64 : 0x38cf19 (0x3a92880 0x0 0x24f0bf84 0x499038)
    0x24f0bf94 : 0x38cc3d (0x3a94d40 0x6103 0x0 0x1)
    0x24f0bfd4 : 0x197b19 (0x3a94d40 0x0 0x3bc0d48 0x14) Backtrace terminated-invalid frame pointer 0x0
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.AirPortAtheros5424(104.1)@0x930000
    dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x698000
    dependency: com.apple.iokit.IOPCIFamily(2.0)@0x566000
    dependency: com.apple.iokit.IO80211Family(112.1)@0x917000

    Kernel version:
    Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


    *******





    MacBookPro 17"   Mac OS X (10.4.7)   2.16Ghz, 2GB RAM
  • Chus Level 1 Level 1 (0 points)
    I'm getting frustrated. My MBP is getting very hot and last Sunday I got that gray screen shut down message again.

    -Now I have some application crashes: Finder and Safari for example.
    -My MPB is restarting itself randomly. I noticed that after I left my laptop inactive for a while or put it to sleep. Then I come back and I have to enter my password to log in and restart my applications.

    Dear Steve Jobs,
    I think that porting of the OS X Tiger to the Intel processor did not go as smooth as you said. I can show you the many logs crashes, or hiccups as you call them. An example of the panic log is below.

    When are getting this OS problems fixed?

    Thanks.


    Sun Sep 10 13:17:50 2006
    panic(cpu 1 caller 0x0019CADF): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
    CR0: 0x80010033, CR2: 0x222a001c, CR3: 0x00db5000, CR4: 0x000006a0
    EAX: 0x222a0000, EBX: 0x06dc4c04, ECX: 0x03d11000, EDX: 0x0296a000
    ESP: 0x222a001c, EBP: 0x24f63ac8, ESI: 0x06dc4c14, EDI: 0x00000000
    EFL: 0x00010206, EIP: 0x005c8fa1, CS: 0x00000008, DS: 0x00000010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x24f63938 : 0x128b5e (0x3bc46c 0x24f6395c 0x131bbc 0x0)
    0x24f63978 : 0x19cadf (0x3c18e4 0x1 0xe 0x3c169c)
    0x24f63a28 : 0x197c7d (0x24f63a3c 0x24f63ac8 0x5c8fa1 0x3a0048)
    0x24f63a34 : 0x5c8fa1 (0x3a0048 0x79e0010 0x10 0x10)
    0x24f63ac8 : 0x5f8490 (0x6dc4000 0x0 0x9000 0x0)
    0x24f63ba8 : 0x5f8970 (0x6dc4000 0x0 0x0 0x426)
    0x24f63c78 : 0x5c1b31 (0x6dc4000 0x0 0x0 0x426)
    0x24f63d38 : 0x3a3d5c (0x3f7f800 0x40cfcac 0x1c 0x0)
    0x24f63d88 : 0x18a83d (0x3f7f800 0x7 0x40cfcac 0x1c)
    0x24f63dd8 : 0x12b389 (0x40cfc84 0x3e4556c 0x0 0x0)
    0x24f63e18 : 0x124902 (0x40cfc00 0x0 0x48 0x24f63efc)
    0x24f63f28 : 0x193034 (0x24f63f54 0x0 0x0 0x0)
    0x24f63fd8 : 0x19814b (0x439cac8 0x439cac8 0x6dc4c04 0x222a001c) No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbfff39c8
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.ATIRadeonX1000(4.3.2)@0x5ba000
    dependency: com.apple.iokit.IOPCIFamily(2.0)@0x581000
    dependency: com.apple.iokit.IOGraphicsFamily(1.4.3)@0x590000
    dependency: com.apple.iokit.IONDRVSupport(1.4.3)@0x5ab000

    Kernel version:
    Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386
  • oday_ Level 1 Level 1 (0 points)
    I'm trying to get more light shined on this problem so Apple will fix it. I'm getting constant problems when I load network intensive applications like Second Life. Same mbuf errors and only when I use wireless.
    I have created a 'digg' article for this here:
    http://digg.com/apple/MacBookPro_Wifi_causing_kernelpanics

    Please digg the story so Apple will be forced to deal with this instead of burying it. I'm tired of these Kernel Panics.
  • dylanks Level 1 Level 1 (5 points)
    It seems that this issue is due to 802.11-N... has anyone seen this with non-N networks?

    You might try linking to your digg entry from the other digg entry on this: http://digg.com/apple/ManyMacBook_flaws_still_present_despite_earlier_success_story_ondigg
  • Aleksandr Bunin Level 1 Level 1 (0 points)
    I have B and G. Still a lot of kernel panics. When I run my router as G only - there is much less panics, but they do happen
  • dsavage Level 1 Level 1 (5 points)
    Like you, running my N router in G mode helped but did not stop the KPs. Only a B/G only router fixs it for me.



    MacBook Pro   Mac OS X (10.4.7)   802.11N, Pre-N
  • prabbit Level 1 Level 1 (0 points)
    I was receiving the kernel panics as soon as I went wireless with my machine. I called Apple and went through the same routine as several others on this board.

    On the third phone call I was able to talk to a second level support person who immediately said that I should send in my week 16 machine. I did. He told me that I should expect my machine to be repaired and returned in 3-5 business days. Cool, I thought.

    Well, it took 35 days, and eleven different phone calls to Apple for me to get a system. Turns out that they replaced my motherboard/logic board three times. Each time they replaced it, it failed. They also replaced the Airport card and a heat sensor (my machine ran hot, too).

    After Apple having the machine, still unrepaired, for a month, a second level support person said that he would feel much better if he simply sent me a brand new system. Fine with me, because I was agitated that it had been as long as it had and no one was calling me to tell me what was going on. It had been in "test, ready to send" for two weeks.

    Anyway, I have been running my week 35 for two weeks now without a single kernel panic. I have been exclusively wireless almost from the get-go.

    So, to me, anyway, the solution is not G-only, but a new logic board.

    Good luck! Hopefully, it won't take Apple 35 days to replace yours, if you decide to send it in.

    MacBook Pro 15" 2.16Ghz 2GB RAM   Mac OS X (10.4.7)  
  • Kevin Adams3 Level 1 Level 1 (5 points)
    This is a huge scandal!

    This is what I have gathered and concluded from this thread, and from talking directly with Apple:

    It is related to wireless-- disable airport and your machine is solid.

    For whatever reason, different networks cause the kernel panics more often.

    Some machines have it and some don't. I know MBPro users who have machines built at all different times-- some have this problem, some don't. This seems to indicate to me that it is not a software/firmware problem but rather a hardware defect that some MBPros were just born with.

    Notice that this thread started in March. I would not expect a software update people. Apple claims it is unaware of the cause of this problem. This is very doubtful at this point. It seems clear that they are trying to deny that their "best" product is shipping defective.

    This is massive defect that who-knows-how-many thousands of people are experiencing. Please everyone contact Apple and demand an immediate fix or a prompt replacement of the machine for one that works as advertised. At this point it seems clear to me that this is the only fix that Apple will ever have.
  • electrophys Level 1 Level 1 (0 points)
    it has been obvious from the start
    that apple would not admit to the problem

    and if u saw my thread from above; it took 3 MBP for them to get it right

    apple has not been forthright
  • dylanks Level 1 Level 1 (5 points)
    Received my MBP back today... it was away for a week.

    new parts: 630-7757 (logic board), and 603-8214 (no idea)

    Also received new install DVDs. This is the second new logic board in a month. I'll post back if this solves the issue.

    In taking the machine to the Apple Store, they did the "send information to Apple" which is found in system profiler, and he was immediately told to take in the machine and send it off to replace the mother board.

    I hope this works, and I hope you all get yours working as well.
  • lpsoraruf Level 1 Level 1 (0 points)
    did today's airport patch fix the problem?
  • Kevin Adams3 Level 1 Level 1 (5 points)
    Don't want to speak to soon...

    But have been downloading for 10hours wireless without a kernel panic. Seems it may have fixed it.

    Anyone else?
  • G.Favara Level 1 Level 1 (0 points)
    Perhaps mine works too (mbp it's turned on for about 8hrs). That would be great.

    By the way, I'll say "works" for sure in the next days
  • Xod Level 1 Level 1 (0 points)
    Same. So far so good.