Update from 04/09 (possibly kernel) causing system lock ups

It seems that this is happening only on battery power on my laptop. I'll be browsing the internet (nothing very intensive) and my laptop will hard lock: no caps lock toggle, can't ping from another networked PC, shutdown command via power button doesn't work. I just have to hold the power every time this happens. I tested last night and the longest uptime I had on battery was 30 minutes, while I never had a freeze on AC.
Has anyone else experienced this? I don't see anything in /var/log/everything.log, so I don't know of a good way to isolate this, so any advice would be appreciated. Here are my system specs via lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 Ethernet controller: Atheros Communications Atheros AR8132 / L1c Gigabit Ethernet Adapter (rev c0)

I attempted to roll back to a server last synced before the update, however this seemed to cause some problems, so I'm going to try another route. If it's related to ath9k hopefully this will fix it:
http://wireless.kernel.org/en/users/Download/stable/
If anyone has any ideas it would be appreciated....this is one nasty problem.

Similar Messages

Looking at syslogs messages getting set_rtc_mmss: can't update from x to x - kernel

Hello,
   Im just looking at the syslogs im getting from the fabrics.
   I noticed alot of warning about :
%DAEMON-5-SYSTEM_MSG: time reset +0.257072 s - ntpd[5315]
%KERN-4-SYSTEM_MSG: set_rtc_mmss: can't update from 49 to 0 - kernel
%KERN-4-SYSTEM_MSG: set_rtc_mmss: nowtime=1339758026, save_control=0x82, save_freq_select=0x72 - kernel
   To me it looks like the kernel complains when the time get updated by NTP. Someone have those entries in logs also?

Would help to have the version of UCSM you're running.
There's an open bug on a similar issue: CSCti71838   - %KERN-4-SYSTEM_MSG: set_rtc_mmss: can't update from 52 to 6 - kernel
It's a general Nexus OS NTP bug, not specific to UCS. At this stage it appears purely cosmetic and does not affect the system. The bug is still in the "new" state. Please monitor the bug toolkit for updates.
Can you also check that the delta between the UCS current time and NTP server are less than 30min?
I'd suggest you open a quick TAC case, provide the output and request your case be linked to this bug. This will increase the priority to have it resolved.
Regards,
Robert

Will updating from CS6 to CC Indesign cause any unwanted changes to existing CS6 documents?

Will updating from CS6 to CC Indesign cause any unwanted changes to existing CS6 documents?

The update itself will not affect exisiting files, but if you open and save them in CCC you will no longer be able to open them in CS6.

Odd System Lock-Ups [XP-Pro SP3]

Something odd is happening, on my normally, and otherwise stable laptop with XP-Pro SP3.
I have observed that on Fridays, at about 11:30AM MST/USA, I get system lock-ups. Everything just freezes.
I have poured over Event Viewer, and nothing is getting launched at about that time. Really nothing in System, or Applications, from about boot-up, other than my Browser (Chrome). Not one Warning, or Error, and little real activity.
I cannot verify that this happens every Friday (do not remember it on Friday Jan. 13, for instance, but then the Adobe Forum Log-in went down), as I am often out of town. However, and based only on memory, this has now happened about 5 - 6 times, and always late in the morning, and on Fridays.
Normally, I only have my Browser open, though this time also had Windows Explorer minimized. During this AM, I had PrPro, PrE and Photoshop open at times, but none was open, when the lock-up happened.
I tend to suspect something is trying to update, but it's not showing in Event Viewer. A few times, there was a Norton Live Update Scan, but those were usually hours before. Those are not download/installs, as I have Live Update to full manual, and the same for all other such utilities.
Does anyone have any ideas, or perhaps a monitoring utility, that will gather data, better than Event Viewer?
TIA,
Hunt

hmm.... google.... i dont really trust google much....
i used to have something ( i use xp ) that basically I had total control over when to connect to isp etc and disconnect... but for life of me cant remember what it was. that was years ago.
now when i start computer it automatically ( partially this is due to isp of verizon ) connects and then gives me control of computer ( is part of boot and load process now ).
your prob seems to be some kinda scheduled thing is why i was thinking maybe turn stuff ' off ' that might be trying to update or something under the radar ( is part of the system more or less.. components ...)
this area
you wont see this related stuff in event viewer type listings ... and gets kinda complicated to me at least.

Aperture 3.1 - Love Full Screen Mode, Hate The System Lock-Ups

Hi Guys,
I don't know if I'm the only person encountering this issue but Aperture 3 is driving me nuts. While I absolutely love the program and the full-screen mode, what I hate is the frequent lock-ups that force me to completely restart my iMac. Having the application lock-up is highly annoying but at least in "normal" mode I could kill the application from the Dock or Activity Monitor. However, when I'm operating in full-screen mode then I can't switch out of the application and seem to have no option but to completely restart my computer. This problem, which I first started experiencing with version 3.0 but which does seem to have been addressed in version 3.1, is happening so often that I'm afraid now to even use full-screen mode.
This problem only, to my memory, seems to happen when making adjustments but it does not seem to matter which adjustment. In the most recent occurrence the lock-up happened when I cancelled the application of a Crop by clicking the X icon on the Crop HUD.
Does anyone know either a) what might be causing the lock-ups, or b) how I can kill Aperture without having to completely restart my computer?

You could also set up SPACES to see if that works when lock up occurs in full screen
Apple Icon > System Preference > Desktop & Screen Saver > Hot corners
I have bottom left set to spaces
Then drop the mouse to bottom left, 4 windows appear, drag aperture to a seperate window and run there, you desktop is in a different space and can be accessed by bottom left of screen mouse movement (if the mouse works when A3 locks up)

System Lock-ups. What can be wrong?

On to more serious issues.. .
I am experiencing system lock-ups on the brand spanking new computer I just buildt.(Yeah, yeah.. . Anti-static and all other thinkable precautions were taken.. .)
Needless to say it's annoying the hell out of me. I can't work and I can't play with a situation like this.. .
The system just hangs and the only solution is to press the reset button.
This usually happens in games or when scrolling a window. Less frequently it also happens when doing nothing. It only seems like it's getting worse - more frequent that is.
Are there any known issues with TwinMos RAM and nForce2?
The RAM and CPU are running on the same clock. The error persists when running the RAM at it's native clock too.
I'm running Catalyst 4.11 and Bios Information says 113-95702-100.
The BIOS of the MB has not been flashed by me - as out-of-the-box.
Nvidia drivers version 5.10.
No overclocking of any sort of any device.
I will be running the full monty in Memtest x86 over night, but the RAM DIMM is spanking new and has been handeled with the utmost caution. The first five tests returned nothing wrong.
Another peculiar hick-up is that sometimes after the lock-up and after I've pressed the reset button the BIOS seems to take forever to detect the IDE devices. If I power off and on again, the IDE detection happens in a snap. Very, very strange.. .
Edit: I have a sneaking suspicion that it gets worse until I power off/on - after that it will take a longer time for the error to return. I haven't verified this empirically, but I have a hunch.. .
I really hope there's someone with helpful insight to this problem out there!
Thank you for your time.

Woops. Seems like I don't have access rights to the last link.
It seems like downflashing to B30 is the only way to go for me as I'm having *major* stability issues, even with no overclocking.
Heck - I even had to reset and reboot the machine when trying to write this post just now!
I must say I've never experienced such outrageous instability with any of my other MSI MBs before.. . Not from any other make for that matter. This is just incredible.
I'll flash it tomorrow (if I can find a damned floppy somewhere). For now I really have to work.
Fingers crossed!
Thanks again for great input!

Verify Disk results, confusing.. Can they be the cause of system lock ups?

I have been experiencing strange freezes on my Mac Pro 2008 system.
My boot disk is a 50% full 128GB SSD from Crucial and is running beautifully fast however for the past couple of weeks my system often freezes for anything from 3 seconds to 30 seconds and then the Finder restarts.
After the Finder restarts everything continues running smoothly. As if nothing ever happend, no error reports, no apps crashed, nothing.
I have verified disk permissions and verified the disk itself in Disk Utility but I am not quite sure what these results mean and if they could be the cause of these random lock ups.
here are the results:
Verify permissions for “Boot Disk”
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Group differs on "private/etc/hostconfig", should be 0, group is 20.
Permissions verification complete
Verifying volume “Boot Disk”
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Missing thread record (id = 5888152)
Incorrect number of thread records
Checking multi-linked files.
Checking catalog hierarchy.
Invalid volume directory count
(It should be 184294 instead of 184295)
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Boot Disk was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
I would really appreciate it if someone that knows their way around this stuff could help me troubleshoot this.
As for the problem of the system locking up it does not happen in the same application consistently.
Often it happens in Firefox but it could equally often happen when working in Photoshop, browsing files in the Finder or trying to access the Spotlight search via the keyboard shortcut.
When the system locks up I get the spinning beach ball and I can still move the mouse and click and even still access CMD+TAB app switcher, switch spaces and all those things, just applications become non responsive.
If you need any more details please let me know.
Thanks for reading,
Jannis

These are innocuous errors that you may safely ignore. However the disk error is a problem. Do the following:
Repairing the Hard Drive
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

System lock ups when using hard disks

At first I thought I had the same issue as in this thread however after reading his logs I decided that it is unlikely since the topic opener seems to be getting a bunch of
Apr 4 17:00:15 daxteriv slim[708]: (Do:882): GLib-CRITICAL **: Source ID 46 was not found when attempting to remove it
, so I decided to start a new thread.
I am not getting anything in my logs when I look at them after the crashes. It seems as if whatever is causing the issue makes it impossible to write to the drives so nothing seems out of place until after it's too late, and quite obvious that something is wrong. The sole exception to this was some complaint about ata9.00, however this seems to have been a red haring since the complete removal of this drive solved nothing, though it did make the error go away.
I have run memtest, and prime95 (in windows since at the time I didn't want to boot my system) both coming back negative. I also checked for SMART errors, particularly UDMA errors. Again, negative.
Here are some previous threads of mine that I believe to be all related to the same issue:
https://bbs.archlinux.org/viewtopic.php?id=195449
https://bbs.archlinux.org/viewtopic.php?id=193937
https://bbs.archlinux.org/viewtopic.php?id=192704
[edit3] My previous thought was that this was a btrfs issue, however now I think it may be more hardware related.[/edit3]
Last night I was writing urandom to a new drive and I woke up in the morning to see that it had stopped prematurely, but not due to lack of space. The system had not locked up completely, which was new, however, as soon as I did something that accessed the disks (tried using the Gnome Dash), all hell broke loose. I immediately hit the power button, which would start a shutdown. I didn't know about REISUB, or I would have tried that. In anycase the shutdown failed and I had to hard reboot.
The evening before I was playing games just fine and doing normal activities.
Also, the other day, while booted into the live cd I think it started to crash since it was acting extremely bizarre, but I shutdown, successfully, before it could do more than complain a lot. At the time I was in the middle of scrubbing a btrfs volume after a system lock up. I think, but am not certain, that I saw on my motherboard "A5" which, according to the manual indicates "SCSI reset", but I had an extremely bad viewing angle. I know neither if what I think I saw was correct, nor do I know if the system was again in the process of a meltdown.
In general there is no activity that seems to be able to instantly trigger this, though in each case, if my memory serves me well, there was a constant stream of data either to or from a HDD.
My set up is that I have 5 HDDs, and an SSD. One HDD has Windows, my fallback installation of Arch, and daily backups. Another drive, which I just installed a few days ago currently only has single 50GB btrfs partition that is not part of any sort of larger volume. I also have three other drives each with four parttitions each involved in a btrfs volume. At the top is a 175 GB volume in a RAID0 configuration, after that is a 25GB partiton in RAID1, then a 650GB partion (RAID1), and the remainder of the disk (about 80GB) is in single. The RAID0 is has games on it and sometimes for short term storage (a few hours), the 25GBx3 RAID1 is used for Arch as well my ~/.local, ~/.cache, ~/.thunderbird, ~/.mozilla, and ~/.config. The 50GB partition I mentioned is currently doing the job of this volume, and was not mounted last night, but has been before. The 650GBx3 is used for long term storage of just about everything, in particular ~ is mounted here. The single configured volume is used for downloads, storing ISOs and installers. The SSD is used for caching those partitions used in the RAID0 volume with bcache. I DO NOT think this is a bcache issue since the RAID0 volume has never had any errors.
My motherboard is a ASUS X79-DELUXE which has the SATA controllers: Intel X79 Express Chipset, Marvell 9230, ASMedia 1061.
[edit] Oh, I'm on kernel 3.19.2 and btrfs is 3.19.
[edit2] Also, I converted the RAID0 to a single in case that matters.
[edit4] I finished scrubbing and copied my "journalctl -b" output to pastebin. I can't see any thing that might raise any flags. http://pastebin.com/WXpbpTuc
Last edited by nstgc (2015-04-05 16:46:00)

nstgc : it's hard to tell if your problems are memory related, but memtst often needs multiple passes to detect errors.
How many passes did you let it make ?
Is it possible for you to take out say half of the memory chips and see if that changes anything ?
Last edited by Lone_Wolf (2015-05-22 18:27:04)

System lock-ups after upgrading to Tiger

This topic was previously posted in 'Installation & Setup'.
After 3 days (and 18 views) I got no replies.
Maybe that forum was not appropriate, so I decided to try it in this forum.
About 4 months ago I exchanged my 80 GB Hd in favor of an 200 GB Maxtor 6L200P0. One day later I upgraded OS X 10.3.9 to Tiger (retail DVD).
At that time I experienced a frequent (several times a day) lock-up of my system.
No messages, nothing, not even after powering down and restarting.
After some time I figured out that the lock-ups occurred on Internet access. Clicking on a link in Safari, posting messages on Discussions. Even Mail locked the system a few times. Also Corripio (artwork and lyrics finder for iTunes) caused the system to lock.
After that, I decided to perform an Archive & Install (first time after almost 4 years of using this Mac). Except from having to re-install a number of 3rd party apps. the system seemed to perform well. No lock-ups were experienced for a few weeks.
Problem solved, I thought.
Although far less frequent than before, I do experience those annoying lock-ups a few times a week.
Here are my questions:
What could be the cause of the lock-up?
Is is advisable to perform a Clean Install? What advantage do I have of, it opposite to performing an A&I. I'm reluctant to perform a clean install at the moment, because I haven't found a few serials of commercial and shareware applications yet ( I know, I should have written them down :-/ )
Any hints/tips to track down the exact cause?
TIA
M
P.S. ( I do have a bootable complete backup of my HD on an Maxtor Onetouch II )

Hi, M.
1. You wrote: "What could be the cause of the lock-up?"The number of potential causes range from disk corruption or bad applications to serious hardware problems, such as a defective logic board.
2. You wrote: "Any hints/tips to track down the exact cause?"I suggest treating the "lock up" problem — better described as a "freezes and hangs" problem — similar to a kernel panic as the basic troubleshooting and hardware testing steps are virtually the same. See my "Resolving Kernel Panics" FAQ.
It provides a comprehensive roadmap which you should follow from beginning to end, in the order specified in the FAQ.
2. You wrote: "Is is advisable to perform a Clean Install? What advantage do I have of, it opposite to performing an A&I."The term "Clean Install" does not apply in Mac OS X. That is obsolete Mac OS 9 terminology. The closest Mac OS X equivalent to a "Clean Install" is an Archive and Install with the Preserve User and Network Settings option, which it sounds like you've already tried once previously, but you may want to try again as part of the troubleshooting process I outlined above. See my "General advice on performing an Archive and Install" FAQ for some important tips on this process.
The other options are:
• Archive and Install without the Preserve User and Network Settings option: This reinstalls the OS and wipes out both your accounts and your network configuration, but preserves the previous System folder.
• Erase and Install: Erases the hard drive, i.e. Macintosh HD, and reinstalls the OS from scratch, preserving nothing: your accounts, network settings, and everything else on the drive are deleted.
Of those two, and since you have a bootable backup, the second (Erase and Install) would be the second-to-last thing you would try, the last being taking the machine in for service.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

10.5.7 Fundamental Incompatibility with Mac Pro - Screen/System Lock ups

Hi all.
It looks like 10.5.7 is causing a lot of problems, but I think I found a problem that is very fundamental.
First, my system. It's one of the original Mac Pros with Quad Xeons at 2.66GHz. It has 24GB of RAM and several drives in there. I have 3 30" displays plugged into 3 NVIDIA GeForce 7300GT cards. I originally ran a 10.5.7 combo update on my 10.5.6 system, and experienced these problems (detailed below). As I was also running a beta of iTunes and the iPhone SDK (the 3rd release), and beta 2 of Safari 4, I thought this may have caused some trouble. So, I tried an experiment.
I bought a new Corsair 256GB SSD for my startup drive. Loaded my family pack of 10.5.6 onto it as a fresh install, and just applied the 10.5.7 combo update. I get the exact same behavior with no further software. So, this is a fundamental incompatibility of 10.5.7 with a machine having these specs.
Now the problems. They start with the primary (in my case center) screen locking while the other two screens keep working. Meaning, the primary display "works" but none of the windows move, the clock freezes...yet, if you move the mouse there and luckily grab a window, you could move it out onto the other 2 displays and it would allow you to continue to use the application. If you hit the CONTROLkey and scroll up and down (zooming the display in and out) it can sometimes "unlock" the primary display, but then there are many artifacts. For example, the shadows cast by windows appear as plain grey "dashboard esque" blocks and have black stripes at the edges. Also, at random times, the machine just seems to hang completely, and unlock a minute or 2 later. Eventually it locks for good.
Unfortunately this has lead me into a deadlock situation. My iTunes has been updated to the 3rd beta in the iPhone 3.0 SDK release. The library has been modified and only works with that version now. That version requires 10.5.7. So if I revert back to 10.5.6, I lose my iTunes Library or have to wait till the offical version of iTunes is realeased (although that may still require 10.5.7).
I see lots of people are having Firewire (800 in particular) problems, and I have several drives I need on Firewire. It's not a solution to yank them. It all works fine under 10.5.6, of course.
So the question is...is help on it's way? What to do!?
Thanks for any insights.
More info on the system below:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 24 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
SMC Version (system): 1.7f10
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x8
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-2
PCIe Lane Width: x8
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-3
PCIe Lane Width: x4
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
ATA Bus:
SONY DVD RW DW-D150A:
Model: SONY DVD RW DW-D150A
Revision: 1.MD
Serial Number:
Detachable Drive: No
Protocol: ATAPI
Unit Number: 0
Socket Type: Internal
Low Power Polling: No
Power Off: No
TSSTcorpCD/DVDW SH-S162L:
Model: TSSTcorpCD/DVDW SH-S162L
Revision: LC02
Serial Number:
Detachable Drive: No
Protocol: ATAPI
Unit Number: 1
Socket Type: Internal
Low Power Polling: No
Power Off: No
FireWire Bus:
Maximum Speed: Up to 800 Mb/sec
Built-in Hub:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
FreeAgent Go FW:
Manufacturer: Seagate
Model: 0x2200
GUID: 0x20370200105F82
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 200 Mb/sec
Sub-units:
FreeAgent Go FW Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level: 410G
Sub-units:
FreeAgent Go FW SBP-LUN:
Capacity: 149.05 GB
Removable Media: Yes
BSD Name: disk5
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
Seagate149GBTote:
Capacity: 148.73 GB
Available: 132.95 GB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk5s2
Mount Point: /Volumes/Seagate149GBTote
Unknown Device:
Manufacturer: Unknown
Model: Unknown
GUID: 0x0
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
OEM ATA Device 00:
Manufacturer: OEM
Model: 0x0
GUID: 0x30E102E0454B7D
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 200 Mb/sec
Sub-units:
OEM ATA Device 00 Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level:
Sub-units:
OEM ATA Device 00 SBP-LUN:
Capacity: 931.51 GB
Removable Media: Yes
BSD Name: disk4
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
TimeMachine:
Capacity: 931.19 GB
Available: 606.63 GB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk4s2
Mount Point: /Volumes/TimeMachine
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Memory Slots:
ECC: Enabled
DIMM Riser A/DIMM 1:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02007D11
DIMM Riser A/DIMM 2:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02006013
DIMM Riser B/DIMM 1:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x0200711F
DIMM Riser B/DIMM 2:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02007012
DIMM Riser A/DIMM 3:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xA4730244
DIMM Riser A/DIMM 4:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0x70780241
DIMM Riser B/DIMM 3:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xE4760245
DIMM Riser B/DIMM 4:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xF0770241

I can only tell you that I've run 10.5.7 on my Mac Pro, same model as yours, without any problems. As a beta tester my Mac Pro was the main hardware on which 10.5.7 was tested. I currently have it installed on a first generation iMac, MacBook, and MacBook Pro as well as a second generation MacBook Pro. So far not a single problem.
But, I don't have multiple video cards nor do I use any beta version of iTunes (didn't know there was one since each system upgrade includes the current release) but I do use the Safari 4 Beta - the most recent version just released when 10.5.7 was released.)
I can suggest you read the following about updates of system software:
Essential Steps Before Updating OS X!
Please do things right before updating OS X in order to avoid problems.
A. Repair Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
B. Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button. This step can be skipped if the destination has already been freshly erased.
4. Click on the Restore tab in the DU main window.
5. Select the destination volume from the left side list and drag it to the Destination entry field.
6. Select the source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
Destination means your backup drive (should be erased first.)
Source means your startup drive or volume.
C. Download the Standalone Combo Updater from Apple.
Be sure you quit all running applications and disconnect all peripherals (except original keyboard and mouse) before running the installer. When the installer is running do not use the computer in any way other than to respond to an installer dialog.
Install the update by double-clicking on the installer package icon. When the installation is completed Restart the computer. Your computer will boot twice - this is normal. Upon completion of the update use Disk Utility to repair permissions. Not all permissions will seem repaired. You will get spurious reports regarding permissions related to iTunes, Front Row. These can be ignored. They will appear every time you repair permissions.
Following these basic steps should prevent most if not all updating problems. Note that if you have unrepairable disk problems reported in Step A then DO NOT update your system until those problems are resolved.
If you find that you did not follow these suggestions, then you might consider reinstalling OS X and going about the process properly in the hope of a successful result:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

System lock ups

lately i've been having a lot of system lockup problms.. you know the ones where that spinning rainbow balls shows up on the screen. you know i never had a problm running adiumx firefox and itunes at the same time, but lately i don't know if its the updates or what, but i'm getting a lot of lock ups, to the point where i can't play videos on itunes, or quicktime without it freaking out and freezing every couple seconds, or when trying to load firefox it take 10 15 secs, and then forever to actually get to a webpage, i do notice when i turn of growl i don't have as many problms, any suggestions.
powerbook g4
mac os x 10.4.8
1ghz processor
512mb ddr sdram
80 gig hd
dvd/cd-rw
got all the latest mac updates, and updates of most of the softwares i have on this computer
12" in powerbook Mac OS X (10.4.3)

teckie:
RAM can very likely be a part of your issue. If your 12" PB is one of the last 3 models it came with 256 MB of RAM. Considering the issues you are having you should consider maxxing it out to 1.25 GB.
ali b. mentioned your HDD. If your HDD has less than 10-20% free space it can contribute to the issue you are experiencing. It also increases the risk of directory issues, consequent data loss and even a crashing HDD.
Thirdly, I am not sure what maintenance procedures you use. But you should consider at least running Unix Maintenance scripts using a utility like MacJanitor, and doing Directory repairs and replacement with a utility like Disk Warrior. In addition, if you have not booted from your install disk and run Repair Disk recently, I suggest you do so.
Take a look at Gulliver's article on Mac OS X Maintenance for some very helpful tips and resources: http://discussions.apple.com/thread.jspa?messageID=607640&#607640
Post back with further questions or comments.
Good luck.
cornelius
Message was edited by: cornelius

Help please updating from 9.04 to 9.1 system stalls

hi to all forum participants,
trying to update an 233 Mhz Imac from 9.04 to 9.1 always produces the same reaction. installation starts, tells me to expect a friendly 8 minutes to finish the update but after 3 or 4 minutes the system freezes up and no progress even after long time waiting.
The main cause for the update is that the old HD didnt boot any more -blinking question mark- and replacing it with the original 4GB HD which had 9.0 on it didnt show the external USB HD. Someone told me that USB support is easy only from 9.1 or better 9.2 on. So trying to update to 9.1 seemed to be the remedy but still hooked up.
Every help welcome
imac Mac OS 9.0.x

Hi, AKG8R -
There was a basic change in Language Kit versions between OS 9.0.4 and OS 9.1 - OS 9.1 is incapable of working with older versions, and since the download updater does not include any Language Kits, it will refuse to install of an older version of a Language Kit is present. Since an OS 9.1 Install CD does include Language Kits, it can replace older versions with newer ones.
There are two solutions that will allow you to use an OS 9.1 download update -
(1) Use a full-install OS 9.0.4 Install CD to remove (uninstall) any language kits.
(2) Remove the Language Kits manually. To do this, open the System file (that's the file [kind = suitcase] named System located loose in the System Folder) - just double-click it. Inside you will find three kinds of files -
• sound files (icon = document with the glyph of a speaker on it);
• keyboard layout files (icon = document with the glyph of a keyboard on it);
• Worldscript files (icon = document with the glyph of a globe on it)
Remove all the Worldscript files to the desktop, or to a folder external to the System Folder.
Restart. You should then be able to use the OS 9.1 download update. Be sure to use the language version of the update that matches the base language version of your OS 9.0.4.
In either case, once you have updated to OS 9.1 using the OS 9.1 download update you will not have the use of any Language Kits - you can not install the older versions and have them work (doing that may kill the OS).
However, you can install the correct versions later on, using any OS 9.1 or later version Install CD. This includes using a model-specific OS 9.1 (or later) Software Install CD, since you do not need to run the OS installer in order to install the Language Kits. It does not include using a Software Restore CD.
To do that, while booted to OS 9.1 insert the OS 9.1 (or later) Install CD. Open the folder named Software Installers. Locate the folder in that named Language Kits, and open it. Inside that folder will be an installer file named Install Language Kits - double-click that file, and follow the prompts to install the Language Kits of your choosing.

Updating from OS X 10.2.8 - System won't recognize password

I recently updated to OS X 10.5.6 directly from 10.2.8. The clerk at the Apple store didn't think that there would be a problem make this large of a leap, but after installing and rebooting, my system would not recognize my existing password. I was able to log in through the installation disc and changed the password, but when I logged back in, it would not accept the changed password (although the hint that I added when I changed the password showed up after three tries, so I have to assume that the changes were accepted and that the system simply isn't making the connection between what I enter as my password and what the password really is).
Any advice on what I can do to get back into my system? (And yes, I'm aware of all of the 'stupid user' issues, such as typing with caps lock on ... I made sure that the problem is not due to user error.)
I also do not have access to the old OS disks, so I can't reinstall the old operating system even if I COULD get into my system to do so.

That's what I'm saying: I did reset my password through the installation disc, but the system still would not accept this new password. I tried this multiple times with a variety of different passwords — both simple and complex. It made no difference.
Any other ideas?

Update from Snow Leopad to Maverick cause email removal from all my IMAP accounts

Hello, i am using mac Mail.app to manage emails for several accounts. Some using POP some using IMAP. Have been working with same settings for more than 2 years in same system. Last week i got a new macbook pro with maverick on, used migration to transfer files & settings. Everything seemed to worked like a charm, until today that i figured out , all my IMAP accounts have Zero inbox on my machine! My machine is already synced with cloud, that means all emails have been deleted from cloud as well. Nothing left in trash or in any folder.
All these years i had copies of my emails in Cloud, somehow something has been really wrong.
Unfortunately i had no backpack, Filevault was disabled and had just bought my new air capsule but havent configured it yet .
Thanks in advance,
C
Already posted in google forums. Link
What i managed to do so far is to use a software called iSkySoft data recovery. Havent managed to recover yet because it requires registration. Does apple has any solution for

Found it finally.
They show up when you select any email account. Select Account Information tab, then use pull down under Outgoing Mail Server (SMTP).
That pull down also has Edit SMTP server list, where you can remove the un-used SMTP's.

Can switching from CRT to LCD monitors cause system problems?

My 9.1 locks up periodically (but the cursor still moves) since I replaced two 20" CRT monitors with two Samsung 19" LCD monitors. Could this affect the performance of my machine? I've tried everything else to address the freeze problem but recall the issue started when I installed the LCD monitors. Anything I can do?

Studedot,
You may have issues with the amount of video memory depending on the resolutions of the new LCD screens.
I find LCD screens go up to insane resolutions, way more than the corresponding size CRT monitor, ie. a 17in Dell LCD monitor with higher resolution than a 21in CRT.
It shouldn't cause crashes or freezes, but may cause -redraw problems when closing / moving windows in 2D and playing 3D games.

Update from 04/09 (possibly kernel) causing system lock ups

Similar Messages

Maybe you are looking for