Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: fyngyrz
fyngyrz Author
User level: Level 1
5 points

You (me!) must now reboot your computer

Just in the last two weeks, I have often found my PPC mini sitting with a dimmed screen and a message in black that tells me that I must reboot. Twice it did it while I was sitting in front of it. Once when editing a forum post (Kuro5hin.org) and once while typing into a text editor. When this happens, nothing responds; mouse, keyboard, etc. So I can't reboot, but there is the power button. So I hold it, power down, and then power back up, and all appears to be well. Until it does it again a few hours or days later.

When the machine reboots, it offers a dialog that has the option "report". I click that, and the dialog goes away, but there is no other response; the machine is booted and waiting for more from me. No report I am aware of sent, and certainly nothing is shown to me as the dialog seems to imply.

This has happened about 8 to 10 times in the last two weeks. The mini has been totally stable since I bought it, which was a few weeks after the original minis first came out.

This mini has been supplying me with wifi for other items (a playstation 3, a wii, my macbook pro) from its ethernet connection, and again, has been fine at that. It has all the options for the time it was purchased. A gig of ram, the 80 gb drive, the modem, the bluetooth, the wifi, the superdrive. It's been a real warrior and converted me to the Mac. I would like to save it, if possible.

Does anyone have any ideas, or places I should start looking, to see what is going on?

I have varied what software I use (normally I use Omniweb, been using firefox, normally leave omnioutliner running, haven't been, normally use textEdit, been using textwrangler instead, normally use Terminal, been using iTerm instead) but none of this has eliminated the crashing, so I presume its not a major app with problems. I also use pinki, ikey, konfabulator, alarm clock 2, have bluetooth on (for my palm) and have Korean keyboard input available but not on. These have all been running forever, and have not been updated as far as I know. I am running 10.4.8, and software update reports nothing to get for me. No new widgets of either konfabulator or apple varieties. Basically, other than Apple updates, no changes in the last few months.

The machine backs itself up to an external USB drive every morning at 5am using SuperDuper. So far (so far as I know, anyway), no data loss from any of these shenanigans, other than what I was typing at the time.

Thank you. Any and all suggestions welcome.

--Ben



2 Mini PPC, 1 Mini dual-core, 1 Macbook Pro Mac OS X (10.4.8) I also run linux and windows

Posted on Feb 11, 2007 9:47 PM

Reply
15 replies
User profile for user: fyngyrz
fyngyrz Author
User level: Level 1
5 points

Feb 11, 2007 9:57 PM in response to fyngyrz

I found the following panics, which seem to implicate the wifi:

Sat Jan 27 15:47:23 2007


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000004C PC=0x00000000006EC714
Latest crash info for cpu 0:
Exception state (sv=0x2E41BC80)
PC=0x006EC714; MSR=0x00009030; DAR=0x0000004C; DSISR=0x40000000; LR=0x006EC66C; R1=0x177DBB50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x006EC66C 0x006F390C 0x006F4F5C 0x006E8A84 0x006F7E98 0x006F7D88
0x006DC3C8 0x00700D08 0x0003C884 0x000A9314
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(405.1)@0x6bd000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5f6000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
Proceeding back via exception chain:
Exception state (sv=0x2E41BC80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x3A063A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780
Proceeding back via exception chain:
Exception state (sv=0x2E41BC80)
PC=0x006EC714; MSR=0x00009030; DAR=0x0000004C; DSISR=0x40000000; LR=0x006EC66C; R1=0x177DBB50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x006EC66C 0x006F390C 0x006F4F5C 0x006E8A84 0x006F7E98 0x006F7D88
0x006DC3C8 0x00700D08 0x0003C884 0x000A9314
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(405.1)@0x6bd000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5f6000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
Exception state (sv=0x3A063A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
*******

Thu Feb 1 10:18:45 2007


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000004C PC=0x00000000006EC714
Latest crash info for cpu 0:
Exception state (sv=0x3B448A00)
PC=0x006EC714; MSR=0x00009030; DAR=0x0000004C; DSISR=0x40000000; LR=0x006EC66C; R1=0x177B3B50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x006EC66C 0x006F390C 0x006F4F5C 0x006E8A84 0x006F7E98 0x006F7D88
0x006DC3C8 0x00700D08 0x0003C884 0x000A9314
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(405.1)@0x6bd000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5f6000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
Proceeding back via exception chain:
Exception state (sv=0x3B448A00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2D251780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780
Proceeding back via exception chain:
Exception state (sv=0x3B448A00)
PC=0x006EC714; MSR=0x00009030; DAR=0x0000004C; DSISR=0x40000000; LR=0x006EC66C; R1=0x177B3B50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x006EC66C 0x006F390C 0x006F4F5C 0x006E8A84 0x006F7E98 0x006F7D88
0x006DC3C8 0x00700D08 0x0003C884 0x000A9314
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(405.1)@0x6bd000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5f6000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
Exception state (sv=0x2D251780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
*******

Thu Feb 1 18:15:08 2007


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000004C PC=0x00000000006EC714
Latest crash info for cpu 0:
Exception state (sv=0x3AC5C500)
PC=0x006EC714; MSR=0x00009030; DAR=0x0000004C; DSISR=0x40000000; LR=0x006EC66C; R1=0x177A3B50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x006EC66C 0x006F390C 0x006F4F5C 0x006E8A84 0x006F7E98 0x006F7D88
0x006DC3C8 0x00700D08 0x0003C884 0x000A9314
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(405.1)@0x6bd000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5f6000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
Proceeding back via exception chain:
Exception state (sv=0x3AC5C500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2D25D280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780
Proceeding back via exception chain:
Exception state (sv=0x3AC5C500)
PC=0x006EC714; MSR=0x00009030; DAR=0x0000004C; DSISR=0x40000000; LR=0x006EC66C; R1=0x177A3B50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x006EC66C 0x006F390C 0x006F4F5C 0x006E8A84 0x006F7E98 0x006F7D88
0x006DC3C8 0x00700D08 0x0003C884 0x000A9314
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(405.1)@0x6bd000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5f6000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
Exception state (sv=0x2D25D280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
*******

Sun Feb 11 21:02:51 2007


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000004C PC=0x00000000006EC714
Latest crash info for cpu 0:
Exception state (sv=0x2D978500)
PC=0x006EC714; MSR=0x00009030; DAR=0x0000004C; DSISR=0x40000000; LR=0x006EC66C; R1=0x17833B50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x006EC66C 0x006F390C 0x006F4F5C 0x006E8A84 0x006F7E98 0x006F7D88
0x006DC3C8 0x00700D08 0x0003C884 0x000A9314
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(405.1)@0x6bd000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5f6000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
Proceeding back via exception chain:
Exception state (sv=0x2D978500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2D251780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780
Proceeding back via exception chain:
Exception state (sv=0x2D978500)
PC=0x006EC714; MSR=0x00009030; DAR=0x0000004C; DSISR=0x40000000; LR=0x006EC66C; R1=0x17833B50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x006EC66C 0x006F390C 0x006F4F5C 0x006E8A84 0x006F7E98 0x006F7D88
0x006DC3C8 0x00700D08 0x0003C884 0x000A9314
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleAirPort2(405.1)@0x6bd000
dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x5f6000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
Exception state (sv=0x2D251780)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
*******
Reply
User profile for user: fyngyrz
fyngyrz Author
User level: Level 1
5 points

Feb 12, 2007 7:31 AM in response to fyngyrz

Given that the panics seem to implicate the wifi, perhaps it would be helpful if I describe how I use the wifi.

The mini is connected via ethernet to my lan, and thence the Internet through a hardware firewall.

The mini acts as a wifi base station that has a number of clients. One is a PS3, one is a Wii. The PS3 is rarely used (because as a Blueray player, it only works in 480p, doesn't work in 720p for movie playback.) So it is off, and I don't think it is complicit in this. The Wii is mostly off, but it does get on the net while it is off. It seems to work fine; I've upgrade the Wii and exchanged avatars and emails using the Wii's facilities. I did have to hand-configure the Wii and jam an IP of the proper range in there, as it would not link up automatically with the mini's wifi, which I thought was odd.

I also use the mini to serve as the net connection for my Macbook Pro. That also works fine. When my sons (3 of them) are here, they all have notebooks, windows and macs, and no one has had any trouble hooking up.

The network is open, that is, no wep, passwords, MAC addresses or any of that, just attach and go (we're very rural, visitors are welcome... there's no one close enough to hork bandwidth without us being able to look out the window and laugh at them, sitting in the -10F cold. 🙂 I suppose someone could be using a very high gain antenna from a couple of miles away, but at this point, I'd discount that.

I occasionally hook up my palm, and my sweetheart's palm, and our PSPs, and all of that has worked perfectly as well.

So the wifi is well used, and has been for some time. It is only in the past couple of weeks I've seen these crashes. And the only thing I remember doing is upgrading via the Apple software update facility. Vaguely. There's probably a record of that, no? Anyone know where that record might be kept in the system?

Right now, I've turned the wifi off (sniffle) and I'm hoping that will get me into the no-crash zone. Hard to say, because it isn't a dependable crash, but if it goes for a few weeks, then I guess that's a useful datapoint.

I can turn wifi on using something else, I've got a dual core mini that could serve, I'll have to reconfigure it's netname and so on so everything else thinks it is my original mini. I'd prefer to use the PPC mini as my wifi source, though, so I am VERY interested in fixes, ideas, etc.

2 Mini PPC, 1 Mini dual-core, 1 Macbook Pro Mac OS X (10.4.8) I also run linux and windows
Reply
User profile for user: AndyO
AndyO
User level: Level 6
17,064 points

Feb 19, 2007 12:49 PM in response to fyngyrz

I think the odds are beginning to favor a bug in the
Apple PPC WiFi implementation.


Perhaps in your system, but clearly not in a broader sense since it's not been an issue reported here other than your own.

My own PPC minis function exclusively on wifi, and have shown no problems at all. One with an after-market kit and the other factory fitted.
Reply
User profile for user: fyngyrz
fyngyrz Author
User level: Level 1
5 points

Feb 20, 2007 7:27 PM in response to AndyO

Perhaps in your system, but clearly not in a broader
sense since it's not been an issue reported here
other than your own.


There are several issues here that may not be commonly duplicated; particularly the PS3 and Wii clients. There is no question that the panic logs point right to the wifi; there is no question that I've had zero problems since turning off the wifi; there is no question that the problem is of recent vintage (which could implicate the Wii, which is recent, or an Apple update, similarly recent.

I'm not saying this is a bug that affects everyone; however, clearly, it is a bug. Why? Because, simply put, the machine should not crash. If it crashes, then the wifi system is running into something it cannot handle. The CPUs ability to run is not dependent upon proper functioning of the wifi module. Given that the CPU subsystem is running ok, crashes occur when programs lose their tiny little minds. Next I know that generally speaking, the PPC's wifi is fine. I can connect to it with just about anything and it shares the ethernet connection just fine. But those two clients, particularly the Wii, may have wifi conversations on their own (in fact, the Wii shows a status LED that indicates it does - around the CD drawer.) Which may - may, mind you - be the root of the problem. I'm just guessing on that front, but I am not guessing about the crashes. They're real, and they happen.

So what we end up with here is a bug that shows up in my situation, or an intermittent hardware failure that isn't a problem unless the wifi is on.

The Intel machine is still running fine; which I can live with, actually, but it would seem that the optimum result for the community is to determine what is going on, rather than resting on work-around laurels.

2 Mini PPC, 1 Mini dual-core, 1 Macbook Pro Mac OS X (10.4.8) I also run linux and windows
Reply
User profile for user: AndyO
AndyO
User level: Level 6
17,064 points

Feb 21, 2007 4:36 AM in response to fyngyrz

kdb1 is absolutely right - if you are firmly set on your problem being caused by a bug in the manner you state, then it is clearly hard to provide you with assistance were that not to be the case since you'll dismiss other possibilities.

That your system crashes is obvious. The cause is far from it.
Reply
User profile for user: Boece
Boece
User level: Level 5
6,264 points

Feb 21, 2007 4:58 AM in response to fyngyrz

So what we end up with here is a bug that shows up in my situation, or an intermittent hardware failure that isn't a problem unless the wifi is on.
The Intel machine is still running fine; which I can live with, actually, but it would seem that the optimum result for the community is to determine what is going on, rather than resting on work-around laurels.

All software has bugs. Usually the most obvious bugs are eliminated during testing.

I don't think that anyone participating in this forum is in a position to fix any bugs in the OSX kernel or the airport drivers.

It appears that you problem is co-incident with the latest software updates and with adding addition wireless clients to your network.

If you want to get the mini's wifi running again, it appears that the two most apparent options are to back out of the latest airport update and/or remove the latest wireless client from your network.

Of course it it also possible that the software on your mini is corrupt and the problem could be solved by a re-install of the OS.

(BTW given that you are rural, I trust that all of your equipment is connected to hefty Uninterruptible Power Supplies - UPSes.)
Reply
User profile for user: fyngyrz
fyngyrz Author
User level: Level 1
5 points

Mar 12, 2007 12:32 AM in response to Boece

(BTW given that you are rural, I trust that all of
your equipment is connected to hefty Uninterruptible
Power Supplies - UPSes.)


Yes, everything is on UPS; there are no power issues at all. It is also worth noting since I'm in here anyway, that I'm still 100% crash free since I handed the wifi network over to the Intel mini.

The Intel mini, however, is having its own wifi problems. Which pretty much rules out the corruption theory. The other wifi clients had already been removed from the situation, so they're not causing the problems, and that doesn't leave a lot left other than system updates.

I do appreciate the replies. But you're right. This forum isn't Apple, and you guys can't fix bugs. I'll have to wait for Apple to fix them.
Reply
User profile for user: fyngyrz
fyngyrz Author
User level: Level 1
5 points

Mar 12, 2007 12:51 AM in response to kdb1

You seem to have your mind set on your problem being
a bug, how can anybody help you if you don't look for
other reasons for your problem,files and drivers can
still become corrupt in OS X just as they can in
Windows.


I'm sorry, if someone suggested looking at a particular file or driver, I seem to have missed that suggestion. I certainly didn't say I would not look. I'm not at all sure where you got this idea. I do not know where to look or what to look for.

If you have a suggestion as to where to look, by all means, simply post your suggestion and I will do my best to follow it up.

Someone else posted about "rolling back" the airport update. Is this easily done? If so, how?
Reply
User profile for user: fyngyrz
fyngyrz Author
User level: Level 1
5 points

Mar 12, 2007 12:53 AM in response to Boece

If you want to get the mini's wifi running again, it
appears that the two most apparent options are to
back out of the latest airport update and/or remove
the latest wireless client from your network.


The clients have been removed. This did not solve the problem. How would I go about backing out of one (or more) airport updates?
Reply

You (me!) must now reboot your computer

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up