Os 10.8.5 shutdown
I have a iMac that is running 10.8.5 mountain lion it will occasionally shuts down unexpectedly. Need to unplug wait and the plug back in. Was told by a Genius Bar tech the problem may be with Mountain Lion. To me this seems like a hardware problem not software. The computer owner does not want to upgrade to Yosemite. If the upgrade would definetly fix the problem we would concider it. The ted mentioned a specific problem with power shutdown with Mountain Lion and I did not write it down could some one help?
I was just there today, the first tech after about a half hour stated the power supply should be replaced. Because we are in the middle of tax season I did not want to leave the machine with them for a week. I called them up after I got home and because I did not receive a email detailing my visit. After I reviewed my story with the new guy he said I should load Yosemite because it had a fix for unexpected shutdown. So I tend to believe you a power issue should be hardware and not software. This power issue in particular because the machine will not restart for 5 to 10 minutes as if it needs to cool down first.
Similar Messages
-
Unable to capture startup and shutdown event of Photoshop in automation Plugin.
Hi,
I am creating an automation plugin and I want to register some events. I have seen listener plugin sample to register event in startup and unregister event in shutdown. I have used same code in my plugin but I am unable to capture the startup nad shutdown event of Photoshop. On clicking the menu item of my plugin the calls come inside the AutoPluginMain but during the startup or shutdown of plugin, the calls does not come inside the AutoPluginMain.
I am unable to detect the cause of the problem. Can someone please giude me??
Thanks in advance.Hi Tom,
Thanks for the suggestion.
Yes, I am working on Windows. As you suggested, I compiled .rc file but the compile option for .r file was disabled. After compiling the .rc file, I again rebuild the complete project and tested my build. But still I was not able to achive the desired result.
Any other thing that I need to do to make it work?
Thanks -
Lock ups, Difficult starts, reboot/restart = shutdown
My computer locks up and will not "Restart", if I tell it to "restart" it shuts down. The "Restart" button also causes the computer to shutdown.
I checked logs and found this stuff:
kernel: ApplePMU::PMU FORCED SHUTDOWN, CAUSE = -122
Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x00000000000000D4 PC=0x0000000000266EA0
Latest crash info for cpu 1:
Exception state (sv=0x259C2500)
PC=0x00266EA0; MSR=0x00009030; DAR=0x000000D4; DSISR=0x40000000; LR=0x00266EE8; R1=0x11F03E40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00266EAC 0x00266E10
Proceeding back via exception chain:
Exception state (sv=0x259C2500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x24F26500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
panic(cpu 1): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x259C2500)
PC=0x00266EA0; MSR=0x00009030; DAR=0x000000D4; DSISR=0x40000000; LR=0x00266EE8; R1=0x11F03E40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00266EAC 0x00266E10
Exception state (sv=0x24F26500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
I also ran a Hardware Test and all the hardware seems ok.
I've taken the battery out of the PMU and it doesn't seem to have any issues starting without that battery in place.
I'm really confused. Why all of a sudden would my computer hate me like this?Hi, Daniel!
You can use this Apple Document to test your QS power supply with a voltmeter, without having to remove it from the Mac. It references a different model, but the only difference is that the voltage at pin 22 is 25 volts on a QuickSilver PSU rather than the 28 volts shown for the Gigabit Ethernet Mac. The procedural steps are the same...
Does the Mac restart properly with the battery removed from the logic board? Does the battery test out okay, or can you swap it with another one?
Gary -
Hello All,
I have a 15" i7 Macbook Pro from early 2011. The past few weeks, it has been getting increasingly difficult to get on my computer. It takes the mac laptop two or three tries to boot successfully. It would turn on, show gray screen, shut down, turn on again, show gray screen, shutdown, and then turn on, show gray screen, before it can finally get to the dark gray log-in screen. Even when I finally get logged in to start working, thinking it would be okay now, it shuts down randomly.
I've ruled out the possibility of a software problem because I've just done a clean re-install of Mac OS X Mavericks on my computer just yesterday.
I did upgrade the RAM recently, about a month and a half ago, from 4GB to 16GB, I went to the apple store four days after that upgrade to have them do a hardware test, and clean the inside of my laptop, which helped with previous heat issues. When they did the hardware test, the hardware was all registered as fine from their system.
I've tried resetting the SMC, PRAM, and doing the internet recovery hardware test, but to no avail. I thought I could at least find out what parts needed to be replaced from the hardware test but it seems that when the hardware test is almost finished, the computer just shuts down, So I am unable to see the results.
My computer is also having battery issues, under battery condition, it says "replace now," parts have been ordered, waiting for arrival. But if the battery health is low, it should still boot up fine, it would just hold a significantly less charge.
Could this be a hard drive issue?
Has anyone had similar symptoms and how was it resolved?
Does anyone know what I can do to alleviate this issue?
I haven't had time to take it to Apple because I'm currently taking a 21 credit semester academically. I'm an art and design student so my computer is basically the bane of my existence. Help! Any constructive advice is welcomed!
Thank you so much for your input!
-Christina C.Problem description:
The Hard Disk is failing.
EtreCheck version: 2.0.11 (98)
Report generated November 4, 2014 at 7:59:28 AM EST
Hardware Information: ℹ️
MacBook Pro (15-inch, Early 2011) (Verified)
MacBook Pro - model: MacBookPro8,2
1 2.2 GHz Intel Core i7 CPU: 4-core
16 GB RAM Upgradeable
BANK 0/DIMM0
8 GB DDR3 1600 MHz ok
BANK 1/DIMM0
8 GB DDR3 1600 MHz ok
Bluetooth: Old - Handoff/Airdrop2 not supported
Wireless: en1: 802.11 a/b/g/n
Video Information: ℹ️
Intel HD Graphics 3000 - VRAM: 512 MB
Color LCD 1440 x 900
AMD Radeon HD 6750M - VRAM: 1024 MB
System Software: ℹ️
OS X 10.9.5 (13F34) - Uptime: 0:3:43
Disk Information: ℹ️
TOSHIBA MK7559GSXF disk0 : (750.16 GB)
S.M.A.R.T. Status: Verified
EFI (disk0s1) <not mounted> : 210 MB
HDV4 (disk0s2) / [Startup]: 749.30 GB (712.10 GB free)
Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
MATSHITADVD-R UJ-898
USB Information: ℹ️
Apple Inc. FaceTime HD Camera (Built-in)
Apple Inc. BRCM2070 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Inc. Apple Internal Keyboard / Trackpad
Apple Computer, Inc. IR Receiver
Thunderbolt Information: ℹ️
Apple Inc. thunderbolt_bus
Gatekeeper: ℹ️
Mac App Store and identified developers
Kernel Extensions: ℹ️
/Library/Application Support/Avast/components/fileshield/unsigned
[loaded] com.avast.AvastFileShield (2.1.0 - SDK 10.9) Support
/Library/Application Support/Avast/components/proxy/unsigned
[loaded] com.avast.PacketForwarder (1.4 - SDK 10.9) Support
Launch Agents: ℹ️
[not loaded] com.adobe.AAM.Updater-1.0.plist Support
[loaded] com.avast.userinit.plist Support
Launch Daemons: ℹ️
[invalid?] com.adobe.SwitchBoard.plist Support
[loaded] com.avast.init.plist Support
[loaded] com.avast.uninstall.plist Support
[loaded] com.avast.update.plist Support
[invalid?] com.perion.searchprotectd.plist Support
User Launch Agents: ℹ️
[invalid?] com.avast.home.userinit.plist Support
[loaded] com.google.keystone.agent.plist Support
[invalid?] com.jdibackup.ZipCloud.autostart.plist Support
User Login Items: ℹ️
None
Internet Plug-ins: ℹ️
AdobePDFViewer: Version: 10.1.1 Support
QuickTime Plugin: Version: 7.7.3
JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
Default Browser: Version: 537 - SDK 10.9
User Internet Plug-ins: ℹ️
TroviNPAPIPlugin: Version: 1.0 - SDK 10.9 Support
Google Earth Web Plug-in: Version: Unknown
Safari Extensions: ℹ️
Avast Online Security
Trovi Search for Safari
3rd Party Preference Panes: ℹ️
None
Time Machine: ℹ️
Time Machine not configured!
Top Processes by CPU: ℹ️
16% mds
7% WindowServer
1% loginwindow
1% fontd
1% com.avast.daemon
Top Processes by Memory: ℹ️
120 MB com.avast.daemon
86 MB Google Chrome
52 MB Finder
52 MB WindowServer
41 MB Google Chrome Helper
Virtual Memory Information: ℹ️
13.45 GB Free RAM
1.34 GB Active RAM
944 MB Inactive RAM
1.43 GB Wired RAM
1.11 GB Page-ins
0 B Page-outs -
Macbook problems, hard drive crash, random shutdown, freezes
I bought my macbook used a few months ago, and it worked flawlessly until about 3 weeks ago. The system started freezing and not booting (getting folder icon instead of apple at startup). I ran drive setup and tried to repair the drive, but this did not fix the problem. DiskWarrior also could not fix it. I pulled the drive and installed a new hard drive, as I wanted a larger capacity anyways. All my problems appeared fixed for about two weeks, then similar problems began occurring. I backed up all the files I needed to an external firewire drive and attempted to reformat the new internal drive. Drive Setup says it can not reformat the drive - can't mount it and if it does, the drive disappears while in the process of formatting. I pulled the new drive and am having it replaced under warranty. I am using the firewire drive to run my computer, and this seemed to work fine for a day or two until the computer just started shutting down with no warning. Everything goes black, including the little light on the front of the computer. I have to hold down the power button for 10 seconds before it lets me start the computer back up. I had read this may be a memory issue, so I ran memtest and it says the memory is fine (I need to do it in single user mode still, however). I also tried pulling both sticks of ram. They are both 1GB crucial memory. I put each stick in by itself and tried it in both slots and was able to reproduce the shutdown issue with any ram configuration of either stick.
After all this, I realized the firewire drive was only running 10.5, so I updated all the software through software update, and it is now running 10.5.2. It seems to be working better as I have not experienced a random shutdown yet, but I'm anticipating it may start back up soon. Today, however I experienced a different problem - the screen froze on me and the only way to get anything to happen was to force a shutdown with them power button. It's restarted and seems to be working fine again for now.
I've run some logs and here's some things I've found:
When the latest freeze happened, I got this repeated over 100 times:
Apr 29 11:04:31 jon-turners-macbook quicklookd[536]: CGContextClosePath: no current point.
I've also seen this:
Apr 29 11:18:19 jon-turners-macbook kernel[0]: Previous Shutdown Cause: 3
Apr 29 11:18:19 jon-turners-macbook kernel[0]: GFX0: family specific matching fails
Apr 25 19:19:50 localhost kernel[0]: hi mem tramps at 0xffe00000
Should there be anything else I can check? I would run Apple Hardware Utilities, but I don't have the original disks, just the Leopard installer. I have Disk Warrior, but it seems strange this would happen with multiple systems and drives. I'd like to get Techtool Pro, but haven't had the money/time to order it yet.Thanks for the replies!
Yeah, I think it's the HDD. I was just worried that the RAM was bad and corrupted the HDD or something, but given the symptoms I think you guys are right. Ordered a 7200RPM 320GB HDD off Amazon Prime...will be here tomorrow
I'll post how it goes after I finish installing it. I'm backing up as I type.
I wonder if I can fix the ir port and the sleep indicator light when I install the hard-drive. The sleep indicator light never turns off. It stays on as long as my computer is on, only turns off when I shut it down. -
T500 performance loss and restart issue after low battery shutdown
Hi,
Some days ago I experienced a significant loss in performance of my T500. Unfortunately it seems to be a continuous loss and the games I play, e.g. empire total war that did run ok before are nearly unplayable at the moment.
Additionally, when the computer shuts down due to low battery, it no longer manages to resume windows but always crashs during reboot (black screen and hard disk symbol is moving, no other activity for 10 minutes)
I am working with the standard vista installation and installed all automatic updates, but also every time when I shutdown the computer, no matter how long it has been running (even after 1 minute and after a rebooting 3 minutes ago), the red shutdown symbol in start shows that an update needs to be installed.
any ideas?
Many thanks in advance !
Message Edited by Walky on 06-18-2009 09:39 PM
Message Edited by Walky on 06-18-2009 09:41 PMWell, the problem, seem's to have reoccured: Battery ran out (even the indicator leds on the side didn't show any life), Time reset to 1.1.2001, again some rebooting and setting the time again...
Is this a sign of a degrading battery health status?
It looks like reseting the SMC didn't help after all. -
Hi,
I'll try to be as short as possible. I need a bacth or command file to shut a system down located in my network. The batch file needs to be opened by another program called PowerChute Business Edition use by APC for UPS systems.
I have the following. I can make a batch and command file that will log me onto the remote device and then shut down the device.
net use \\computername /user:administrator password
shutdown.exe -s -m \\computername -t 60When I just double click on the batchfile, it runs and the remote device opens a window saying that it will be shut down in 60 seconds.
Only when my program opens the file, the action doesn't happen.
I tried several other things
NET SEND
opening a program with CALL and START
time /t >> c:\timelog.logAll these work, only the shutdown command doesn't work. I tried several other versions like
shutdown -s -m \\computername -t 60
shutdown /s /m \\computername /t 60
shutdown.exe -s -m \\computername -t 60
shutdown.exe /s /m \\computername /t 60...
Now I contacted APC and in their last mail they said:
The command files must conform to a certain syntax because of java. This also causes problems sometimes.
Now I thought I'd might be using the wrong code because of Java,so I thought of asking it in a Java forum.
Best regards
PeterThe program itself is a program for my UPS. When power is cut off, the UPS will switch to batteries. Now the software can execute a command file or batch file before shutting the connected computer down.
So I want this cmd-file or bat-file to shut a remote computer down. This can be done by NET USE (to log on) and the by SHUTDOWN (to shut it down)
If I want to see what happens when the program opens the batch files I go to work like this:
I write 2 files:
CallShutdown.bat
@START "" "C:\Program Files\APC\PowerChute Business Edition\agent\cmdfiles\shutdown.bat
shutdown.bat
NET USE \\computername /user:username password
SHUTDOWN.EXE -s -m \\computername -t 60
NET SEND computername TESTNow I can see on my own computer a DOS window and that gives me the following information:
c:\PROGRA~1\APC\POWERC~1\agent\>net use \\computername /user:Administrator password
The task is completed
c:\PROGRA~1\APC\POWERC~1\agent\>shutdown.exe -s -m \\computername -t 60
Access denied
c:\PROGRA~1\APC\POWERC~1\agent\>net send computername TEST
The message was send to COMPUTERNAMEAnd on the remote computer I can see a Messenger-Service window with the message TEST in it coming from my computer.
First of all the NET USE command works, but the shutdown command fails because the access was denied.
HOWEVER, when I double click on CallShutdown.bat in Windows Explorer everything works just fine. Logon, shutdown and Net Send.
So I don't know why that shutdown command gets an access denied when I let the program execute it, but when I just use the double click action :o) everything works.
Because I got a message from the helpdesk saying something about syntax for JAVA, I thought I'd give it a go on this forum.
Hope I've been clear in my explanation. Two files, one calling the other. Second one logs on and shuts down the remote computer. -
Directive Bundle - Shutdown workstation no longer works
Our network has been using a directive bundle to shutdown our pc's for over a year now and it had worked quite well up until a couple of weeks ago.
At that point I added an additional requirement to keep it from shutting down a pc on our network, since then the pc's are no longer turning off as they had.
The action is set to shutdown the pc's after 900 seconds(15 minutes) and gives the user the option to cancel. The bundle is associated to 4 different workstation groups. The schedule for each association is set to "recurring" and has both the Distribution Schedule and the Launch Schedule set for 6:45pm M,T,W,T,F.
I originally tried to edit the bundle back to its original state by removing the requirement I had added, they still didn't shut down.
Then I rebooted the ZEN server(10.1.1) in case a service or something had been stopped or affected.
The bundle appears on all the clients under the "assigned bundles" in the agent and shows it is available and effective.
Yet the pc's still do not power off... any ideas?szartman,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/ -
Windows 8.1 Random Slow Startups, "Improper Shutdowns"
Is this the right subforum? I almost chose frezes/hangs but that's not exactly what it is so...
Please note that this is a copy/paste from another forum where I sought help. Today is another day from the one referenced in the indented text below. In fact, my system had a clean and safe boot with no speed issues or stalling tonight. The issue is not consistent. Though I was seeking help at another forum, I grew uncomfortable with the steps asked of me (deleting caches and temp files that I'd rather keep and using a third-party defragger; getting standoffish when I requested explanation for why I was being asked to run three or more "cleaner" programs and if defragging was honestly necessary on a mostly-new machine that just got a clean bill of health from HP) and was brushed aside with something of an attitude. Here's the original info on the issue:
Alright, so, yesterday I noticed that it seemed to take a little longer than usual to start up my laptop (HP Pavilion 17-7042nr with Windows 8.1 64-bit; I've only had it a short amount of time and it was purchased refurbished). I didn't think too much of it, however, since I was starting it at the same time as my seven-year-old Vista machine so by comparison it was still way faster (20+ seconds vs. the old one's 2 minutes). After that, didn't think anything of it...
Today, however, I started it up on its own and it took far too long compared to how it used to behave. I've noticed this a few times in the past, but always figured Windows was adjusting itself after I'd installed stuff etc. But since there was no need for it to do that this time, I got suspicious and started looking in the event viewer. To my shock, it claimed that the last shutdown was improper and that's why it took forever; it was actually rebooting.
Trouble is, as far as I knew, no it most certainly did not shut down improperly. I turned it off using the power button, which is set from the power plan to perform a shut down. It did the normal thing: processed the shut down, turned off the screen, and shortly after turned off all system lights except of course the one to indicate that it was plugged in. All seemed well, and was not slower than usual or anything of that sort. So I have no clue why or how it's shutting down improperly.
But not only that, I tracked it back and several times, as far back as the 19th of February (as well as a couple of times while it was in HP's custody for unrelated maintenance; they apparently did not notice it, either, as it was given a clean bill of health before return) this has been occurring. I've transferred a ton of files, settings, programs, etc. since then so I really didn't want to do a Restore. I did, however, consider it... only to discover that my previous Restore Points before the system was returned by HP have been destroyed. So no chance of going back before the 19th, even if I wanted to (I don't, frankly).
I have no clue what's going on, but here's the events from the first ever time it happened:
the logoff/power down is listed as:
Information 2/19/2015 5:09:11 AM Kernel-Power 109 (103)
-- "The kernel power manager has initiated a shutdown transition."
Information 2/19/2015 5:09:37 AM Winlogon 7002 (1102)
-- "User Logoff Notification for Customer Experience Improvement Program"
after that the next relevant things which involve the boot up:
Information 2/19/2015 4:42:36 PM Kernel-Boot 20 None
-- "The last shutdown's sucess status was true. The last boot's success status was true."
Error 2/19/2015 4:42:36 PM Kernel-Boot 29 None
-- "Windows failed fast startup with error status 0xC00000D4"
Critical 2/19/2015 4:42:45 PM Kernel-Power 41 (63)
--"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
Error 2/19/2015 4:43:14 PM EventLog 6008 None
-- "The previous system shutdown at 4:59:42 AM on 2/19/2015 was unexpected."
Information 2/19/2015 4:43:21 PM Service Control Manager 7026 None
--"The following boot-start or system-start driver(s) did not load: dam"
Those were from the 19 of February, the first time it seems to have happened. The most recent (today) incident is very similar, but not entirely identical.
The shutdown was:
Information 3/17/2015 5:12:16 AM Kernel-Power 109 (103)
-- "The kernel power manager has initiated a shutdown transition."
Upon boot the seemingly relevant bits are:
Information 3/17/2015 4:47:55 PM Kernel-Boot 20 None
--"THe last shutdown's success status was true. The last boot's success status was true."
Error 3/17/2015 4:47:55 PM Kernel-Boot 29 None
--"Windows failed fast startup with error status 0xC00000D4."
Information 3/17/2015 4:47:55 PM Kernel-General 12 None
--"The operating system started at system time 2015-03-17T21:47:45.491075600Z." (( What even is up with that time??? ))
Critical 3/17/2015 4:48:01 PM Kernel-Power 41 (63)
--"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
Error 3/17/2015 4:48:24 PM EventLog 6008 None
--"THe previous system shutdown at 5:12:03 AM on 3/17/2015 was unexpected."
I tried googling, to no avail, other than a suggestion that it might be caused by some sort of system file issue. So I ran "sfc /scannow" in an admin-level command prompt and when it was finished it said: "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios."
I tracked down the log file and it's rather huge but toward the end I found that "Amd64\CNBJ2530.DPB" was corrupted. Naturally, I investigated... But according to the thread I found it's some kind of printer-related thing, and I've never even connected a printer to this system, much less a Canon brand one as the info I found suggested. In fact, the thread I linked claims that it shouldn't cause any huge issues, so... Probably not the cause of my shutdown issues, which are more pressing. Thus, I can't find anything to indicate what's causing this problem.
The only thing I can think of that I had done around the 19th was I was trying to get rid of Beats Audio crap on my laptop. (Don't even get me started on that hot mess!) So I'd been swapping between the Windows default audio drivers and versions of the Realtek High Definition Audio from both HP and Realtek. But I never had a corrupt install and I don't recall installing one over the other without uninstalling first, so I don't know if that's an issue. Somehow, I doubt it, especially since this issue isn't consistent. Then again, I don't consistently use the audio on my computer so who knows. (UPDATE: Used audio extensively, but it managed a clean shutdown after.)
After all lights are off and the system is shut down, unless I've been using it on battery and it needs a charge, I unplug it to conserve energy. I only ever do this if the battery has a full charge, so I don't think that should be an issue even though hybrid shutdown/fast boot is some kind of hibernation-shutdown combination. I'd prefer to keep fast start/hybrid boot enabled because, well, it's convenient... and I'm extremely hesitant to tamper with the UEFI settings etc. But, of course, if that's the only fix then I'd prefer it to possible hard drive damage caused by the supposed/apparent improper shut down.
Also of note: nothing is overclocked or running outside specifications, as far as I know. My system stats are:
Windows 8.1 64-bit
AMD A10-5745M APU
AMD Radeon HD 8610G
UEFI BIOS Mode
Secure Boot Enabled
Any help would be greatly appreciated!
Now, for extra details. Things that were done during the process included looking for unnecessary startup items (not the real issue to be honest; when it doesn't forcibly reboot due to "improper shutdown" the startup is extremely speedy) and looking at some logs. In particular, here's the speccy log created for my system: http://speccy.piriform.com/results/vIEkYCelmSRyJjuJyye2jgD
I also had to run several "cleaner" tools, which included installing CCleaner, though I chose some files I wished to keep / thought may be important to not just delete willy-nilly. I don't like to randomly delete things that could come back and bite me in the rear, after all. And I'm honestly confused how any of that would related to Windows having inconsistent and seemingly random "improper shutdown" issues which cause it to reboot instead of using fast boot. (I'm not saying it's impossible, I'm saying that I don't logically see how it'd make a difference and when I attempted to ask I was brushed aside.)
Like I said, by all appearances it seems to shut down properly. It has also never crashed on me. Nor has it ever blue screened or randomly rebooted. This is very much a silent, behind-the-scenes issue.Hi @Alley_Kitten ,
Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion 17 f042nr Notebook and issues with performance issues or improper shutdowns.
I checked the specs of your system and with what you have posted here you have the incorrect Amd driver installed. Your's as per your product page is a AMD Radeon HD 8610G . I would go to the device manager and remove all graphic driver, check the box for the driver as well.
Here is a document on recovery options that are available. I do use the refresh your pc method with Windows 8. Please read all the documentation before starting the operation.
Hope this helps you out.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping! -
Help - Oracle 8.1.5 service is shutdown by itself
Hi All,
I'm new to oracle.
In my office, we're using oracle 8.1.5, the problem now is the services (under NT 4) sometimes can shutdown by itself. If I check the NT services, it shows that the oracle service is still running. But I can't connect to the database using sql plus, error is instance is shutdown. All I can do up to now is restart the services (Listener and Oracle instance).
What should I do to avoid this problem?
TIA
-AndiHi,
Below is the information from orclALRT.log:
There's a write/open error. At July 21, 21:00PM our backup is start to run.
Is it because the backup software locked some oracle's files ?
But after the error, the next morning July 22 the ORACLE instance is started with no error, even though user can't connect to the database.
TIA
Andi
Thread 1 advanced to log sequence 46212
Current log# 4 seq# 46212 mem# 0: E:\ORANT\ORADATA\ORACLE\REDO01.LOG
Sun Jul 21 21:38:26 2002
KCF: write/open error block=0x11072 online=1
file=1 E:\ORANT\ORADATA\ORACLE\SYSTEM01.DBF
error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because
another process has locked a portion of the file.'
DBW0: terminating instance due to error 1242
Instance terminated by DBW0, pid = 248
Mon Jul 22 03:00:04 2002
Starting ORACLE instance (normal)
Dump file E:\orant\admin\oracle\bdump\orclALRT.LOG
--------- -
[systemd] shutdown takes a long time
Hello.
It takes quite a long time for my system to shutdown. The systemd ArchWiki suggests to log the shutdown like this. I am not quite sure what to look for. I suspect that smplayer or deluged might be the problem. Am I right and furthermore what can I do about it?
Thank you for your time.
Here the shutdown log:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.5.3-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 20120721 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=55614e59-14b9-47c5-a609-fd76662e6403 ro systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 quiet
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009bfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009c000-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000005ffeffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000005fff0000-0x000000005fff2fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000005fff3000-0x000000005fffffff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI 2.2 present.
[ 0.000000] DMI: /MS-7030, BIOS 6.00 PG 11/10/2005
[ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] AGP bridge at 00:00:00
[ 0.000000] Aperture from AGP @ e0000000 old size 32 MB
[ 0.000000] Aperture size 4096 MB (APSIZE 0) is not right, using settings from NB
[ 0.000000] Aperture from AGP @ e0000000 size 32 MB (APSIZE 0)
[ 0.000000] e820: last_pfn = 0x5fff0 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-FFFFF uncachable
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask FFC0000000 write-back
[ 0.000000] 1 base 0040000000 mask FFE0000000 write-back
[ 0.000000] 2 base 00E0000000 mask FFF0000000 write-combining
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] found SMP MP-table at [mem 0x000f4fc0-0x000f4fcf] mapped at [ffff8800000f4fc0]
[ 0.000000] initial memory mapped: [mem 0x00000000-0x1fffffff]
[ 0.000000] Base memory trampoline at [ffff880000096000] 96000 size 24576
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x5ffeffff]
[ 0.000000] [mem 0x00000000-0x5fdfffff] page 2M
[ 0.000000] [mem 0x5fe00000-0x5ffeffff] page 4k
[ 0.000000] kernel direct mapping tables up to 0x5ffeffff @ [mem 0x1fcfd000-0x1fffffff]
[ 0.000000] log_buf_len: 1048576
[ 0.000000] early log buf free: 521388(99%)
[ 0.000000] RAMDISK: [mem 0x37a32000-0x37d10fff]
[ 0.000000] ACPI: RSDP 00000000000f8eb0 00014 (v00 Nvidia)
[ 0.000000] ACPI: RSDT 000000005fff3040 00034 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000)
[ 0.000000] ACPI: FACP 000000005fff30c0 00074 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000)
[ 0.000000] ACPI: DSDT 000000005fff3180 048C1 (v01 NVIDIA AWRDACPI 00001000 MSFT 0100000E)
[ 0.000000] ACPI: FACS 000000005fff0000 00040
[ 0.000000] ACPI: SSDT 000000005fff7b80 000D6 (v01 PTLTD POWERNOW 00000001 LTP 00000001)
[ 0.000000] ACPI: SRAT 000000005fff7cc0 00090 (v01 AMD HAMMER 00000001 AMD 00000001)
[ 0.000000] ACPI: APIC 000000005fff7ac0 0007C (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
[ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x0009ffff]
[ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00100000-0x5fffffff]
[ 0.000000] NUMA: Node 0 [mem 0x00000000-0x0009ffff] + [mem 0x00100000-0x5ffeffff] -> [mem 0x00000000-0x5ffeffff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x5ffeffff]
[ 0.000000] NODE_DATA [mem 0x5feec000-0x5feeffff]
[ 0.000000] [ffffea0000000000-ffffea00017fffff] PMD -> [ffff88005de00000-ffff88005f5fffff] on node 0
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00010000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00010000-0x0009bfff]
[ 0.000000] node 0: [mem 0x00100000-0x5ffeffff]
[ 0.000000] On node 0 totalpages: 393084
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 6 pages reserved
[ 0.000000] DMA zone: 3910 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 6080 pages used for memmap
[ 0.000000] DMA32 zone: 383024 pages, LIFO batch:31
[ 0.000000] Nvidia board detected. Ignoring ACPI timer override.
[ 0.000000] If you got timer trouble try acpi_use_timer_override
[ 0.000000] ACPI: PM-Timer IO Port: 0x4008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: BIOS IRQ0 override ignored.
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] ACPI: IRQ14 used by override.
[ 0.000000] ACPI: IRQ15 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] SMP: Allowing 2 CPUs, 1 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: 000000000009c000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[ 0.000000] e820: [mem 0x60000000-0xfebfffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:2 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88005fc00000 s83392 r8192 d23104 u1048576
[ 0.000000] pcpu-alloc: s83392 r8192 d23104 u1048576 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 386934
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=55614e59-14b9-47c5-a609-fd76662e6403 ro systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 quiet
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] Checking aperture...
[ 0.000000] AGP bridge at 00:00:00
[ 0.000000] Aperture from AGP @ e0000000 old size 32 MB
[ 0.000000] Aperture size 4096 MB (APSIZE 0) is not right, using settings from NB
[ 0.000000] Aperture from AGP @ e0000000 size 32 MB (APSIZE 0)
[ 0.000000] Node 0: aperture @ e0000000 size 256 MB
[ 0.000000] Memory: 1532356k/1572800k available (4635k kernel code, 464k absent, 39980k reserved, 4212k data, 756k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] NR_IRQS:4352 nr_irqs:512 16
[ 0.000000] spurious 8259A interrupt: IRQ7.
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 6291456 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 2009.231 MHz processor.
[ 0.000000] Marking TSC unstable due to TSCs unsynchronized
[ 0.006673] Calibrating delay loop (skipped), value calculated using timer frequency.. 4020.89 BogoMIPS (lpj=6697436)
[ 0.006678] pid_max: default: 32768 minimum: 301
[ 0.006716] Security Framework initialized
[ 0.006725] AppArmor: AppArmor disabled by boot time parameter
[ 0.006963] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.010848] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.012136] Mount-cache hash table entries: 256
[ 0.012496] Initializing cgroup subsys cpuacct
[ 0.012500] Initializing cgroup subsys memory
[ 0.012520] Initializing cgroup subsys devices
[ 0.012522] Initializing cgroup subsys freezer
[ 0.012524] Initializing cgroup subsys net_cls
[ 0.012526] Initializing cgroup subsys blkio
[ 0.012564] tseg: 0000000000
[ 0.012585] mce: CPU supports 5 MCE banks
[ 0.012635] SMP alternatives: switching to UP code
[ 0.018800] ACPI: Core revision 20120320
[ 0.022927] ftrace: allocating 17956 entries in 71 pages
[ 0.030518] ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
[ 0.064541] CPU0: AMD Athlon(tm) 64 Processor 3000+ stepping 00
[ 0.066663] Performance Events: AMD PMU driver.
[ 0.066663] ... version: 0
[ 0.066663] ... bit width: 48
[ 0.066663] ... generic registers: 4
[ 0.066663] ... value mask: 0000ffffffffffff
[ 0.066663] ... max period: 00007fffffffffff
[ 0.066663] ... fixed-purpose events: 0
[ 0.066663] ... event mask: 000000000000000f
[ 0.083576] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.083636] Brought up 1 CPUs
[ 0.083638] Total of 1 processors activated (4020.89 BogoMIPS).
[ 0.084405] devtmpfs: initialized
[ 0.086410] PM: Registering ACPI NVS region [mem 0x5fff0000-0x5fff2fff] (12288 bytes)
[ 0.087408] NET: Registered protocol family 16
[ 0.087567] node 0 link 0: io port [9000, ffff]
[ 0.087570] TOM: 0000000060000000 aka 1536M
[ 0.087573] node 0 link 0: mmio [a0000, bffff]
[ 0.087577] node 0 link 0: mmio [d0000000, fe02ffff]
[ 0.087580] bus: [00, 02] on node 0 link 0
[ 0.087583] bus: 00 [io 0x0000-0xffff]
[ 0.087585] bus: 00 [mem 0x000a0000-0x000bffff]
[ 0.087587] bus: 00 [mem 0x60000000-0xfcffffffff]
[ 0.087627] ACPI: bus type pci registered
[ 0.087696] PCI: Using configuration type 1 for base access
[ 0.088295] bio: create slab <bio-0> at 0
[ 0.088374] ACPI: Added _OSI(Module Device)
[ 0.088376] ACPI: Added _OSI(Processor Device)
[ 0.088378] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.088380] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.089228] ACPI: EC: Look up EC in DSDT
[ 0.093337] ACPI: Interpreter enabled
[ 0.093342] ACPI: (supports S0 S1 S4 S5)
[ 0.093368] ACPI: Using IOAPIC for interrupt routing
[ 0.094190] ACPI: Power Resource [ISAV] (on)
[ 0.099077] ACPI: No dock devices found.
[ 0.099086] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
[ 0.099148] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.099226] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
[ 0.099229] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored)
[ 0.099233] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
[ 0.099236] pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff] (ignored)
[ 0.099238] pci_root PNP0A03:00: host bridge window [mem 0x60000000-0xfebfffff] (ignored)
[ 0.099241] PCI: root bus 00: hardware-probed resources
[ 0.099287] PCI host bridge to bus 0000:00
[ 0.099291] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 0.099293] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.099296] pci_bus 0000:00: root bus resource [mem 0x60000000-0xfcffffffff]
[ 0.099312] pci 0000:00:00.0: [10de:00e1] type 00 class 0x060000
[ 0.099321] pci 0000:00:00.0: reg 10: [mem 0xe0000000-0xefffffff pref]
[ 0.099381] pci 0000:00:01.0: [10de:00e0] type 00 class 0x060100
[ 0.099413] pci 0000:00:01.1: [10de:00e4] type 00 class 0x0c0500
[ 0.099420] pci 0000:00:01.1: reg 10: [io 0xfc00-0xfc1f]
[ 0.099432] pci 0000:00:01.1: reg 20: [io 0x4c00-0x4c3f]
[ 0.099437] pci 0000:00:01.1: reg 24: [io 0x4c40-0x4c7f]
[ 0.099451] pci 0000:00:01.1: PME# supported from D3hot D3cold
[ 0.099470] pci 0000:00:02.0: [10de:00e7] type 00 class 0x0c0310
[ 0.099477] pci 0000:00:02.0: reg 10: [mem 0xfe02f000-0xfe02ffff]
[ 0.099502] pci 0000:00:02.0: supports D1 D2
[ 0.099504] pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.099518] pci 0000:00:02.1: [10de:00e7] type 00 class 0x0c0310
[ 0.099525] pci 0000:00:02.1: reg 10: [mem 0xfe02e000-0xfe02efff]
[ 0.099550] pci 0000:00:02.1: supports D1 D2
[ 0.099552] pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.099567] pci 0000:00:02.2: [10de:00e8] type 00 class 0x0c0320
[ 0.099575] pci 0000:00:02.2: reg 10: [mem 0xfe02d000-0xfe02d0ff]
[ 0.099605] pci 0000:00:02.2: supports D1 D2
[ 0.099607] pci 0000:00:02.2: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.099628] pci 0000:00:06.0: [10de:00ea] type 00 class 0x040100
[ 0.099635] pci 0000:00:06.0: reg 10: [io 0xf000-0xf0ff]
[ 0.099640] pci 0000:00:06.0: reg 14: [io 0xec00-0xec7f]
[ 0.099645] pci 0000:00:06.0: reg 18: [mem 0xfe02c000-0xfe02cfff]
[ 0.099665] pci 0000:00:06.0: supports D1 D2
[ 0.099680] pci 0000:00:08.0: [10de:00e5] type 00 class 0x01018a
[ 0.099696] pci 0000:00:08.0: reg 20: [io 0xe000-0xe00f]
[ 0.099723] pci 0000:00:09.0: [10de:00ee] type 00 class 0x010185
[ 0.099730] pci 0000:00:09.0: reg 10: [io 0x09e0-0x09e7]
[ 0.099735] pci 0000:00:09.0: reg 14: [io 0x0be0-0x0be3]
[ 0.099740] pci 0000:00:09.0: reg 18: [io 0x0960-0x0967]
[ 0.099744] pci 0000:00:09.0: reg 1c: [io 0x0b60-0x0b63]
[ 0.099749] pci 0000:00:09.0: reg 20: [io 0xcc00-0xcc0f]
[ 0.099754] pci 0000:00:09.0: reg 24: [io 0xc800-0xc87f]
[ 0.099779] pci 0000:00:0a.0: [10de:00e3] type 00 class 0x010185
[ 0.099786] pci 0000:00:0a.0: reg 10: [io 0x09f0-0x09f7]
[ 0.099791] pci 0000:00:0a.0: reg 14: [io 0x0bf0-0x0bf3]
[ 0.099796] pci 0000:00:0a.0: reg 18: [io 0x0970-0x0977]
[ 0.099801] pci 0000:00:0a.0: reg 1c: [io 0x0b70-0x0b73]
[ 0.099806] pci 0000:00:0a.0: reg 20: [io 0xb400-0xb40f]
[ 0.099810] pci 0000:00:0a.0: reg 24: [io 0xb000-0xb07f]
[ 0.099834] pci 0000:00:0b.0: [10de:00e2] type 01 class 0x060400
[ 0.099865] pci 0000:00:0e.0: [10de:00ed] type 01 class 0x060400
[ 0.099892] pci 0000:00:18.0: [1022:1100] type 00 class 0x060000
[ 0.099913] pci 0000:00:18.1: [1022:1101] type 00 class 0x060000
[ 0.099931] pci 0000:00:18.2: [1022:1102] type 00 class 0x060000
[ 0.099951] pci 0000:00:18.3: [1022:1103] type 00 class 0x060000
[ 0.100003] pci 0000:01:00.0: [10de:0221] type 00 class 0x030000
[ 0.100017] pci 0000:01:00.0: reg 10: [mem 0xfa000000-0xfaffffff]
[ 0.100025] pci 0000:01:00.0: reg 14: [mem 0xd0000000-0xdfffffff pref]
[ 0.100033] pci 0000:01:00.0: reg 18: [mem 0xfb000000-0xfbffffff]
[ 0.100056] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
[ 0.100111] pci 0000:00:0b.0: PCI bridge to [bus 01-01]
[ 0.100115] pci 0000:00:0b.0: bridge window [io 0xa000-0xafff]
[ 0.100119] pci 0000:00:0b.0: bridge window [mem 0xfa000000-0xfcffffff]
[ 0.100123] pci 0000:00:0b.0: bridge window [mem 0xd0000000-0xdfffffff pref]
[ 0.100147] pci 0000:02:07.0: [1814:0301] type 00 class 0x028000
[ 0.100158] pci 0000:02:07.0: reg 10: [mem 0xfdff0000-0xfdff7fff]
[ 0.100216] pci 0000:02:08.0: [10ec:8139] type 00 class 0x020000
[ 0.100228] pci 0000:02:08.0: reg 10: [io 0x9c00-0x9cff]
[ 0.100235] pci 0000:02:08.0: reg 14: [mem 0xfdfff000-0xfdfff0ff]
[ 0.100260] pci 0000:02:08.0: reg 30: [mem 0x00000000-0x0000ffff pref]
[ 0.100278] pci 0000:02:08.0: supports D1 D2
[ 0.100280] pci 0000:02:08.0: PME# supported from D1 D2 D3hot D3cold
[ 0.100298] pci 0000:02:09.0: [1106:3038] type 00 class 0x0c0300
[ 0.100326] pci 0000:02:09.0: reg 20: [io 0x9800-0x981f]
[ 0.100351] pci 0000:02:09.0: supports D1 D2
[ 0.100354] pci 0000:02:09.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.100371] pci 0000:02:09.1: [1106:3038] type 00 class 0x0c0300
[ 0.100399] pci 0000:02:09.1: reg 20: [io 0x9400-0x941f]
[ 0.100424] pci 0000:02:09.1: supports D1 D2
[ 0.100427] pci 0000:02:09.1: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.100445] pci 0000:02:09.2: [1106:3104] type 00 class 0x0c0320
[ 0.100456] pci 0000:02:09.2: reg 10: [mem 0xfdffe000-0xfdffe0ff]
[ 0.100499] pci 0000:02:09.2: supports D1 D2
[ 0.100501] pci 0000:02:09.2: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.100527] pci 0000:00:0e.0: PCI bridge to [bus 02-02]
[ 0.100531] pci 0000:00:0e.0: bridge window [io 0x9000-0x9fff]
[ 0.100534] pci 0000:00:0e.0: bridge window [mem 0xfdf00000-0xfdffffff]
[ 0.100537] pci 0000:00:0e.0: bridge window [mem 0xfde00000-0xfdefffff pref]
[ 0.100546] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.100629] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[ 0.100813] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
[ 0.100901] pci0000:00: Unable to request _OSC control (_OSC support mask: 0x1e)
[ 0.125942] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[ 0.125994] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[ 0.126043] ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[ 0.126092] ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[ 0.126140] ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.126195] ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[ 0.126245] ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[ 0.126293] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.126341] ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.126391] ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[ 0.126440] ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[ 0.126489] ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[ 0.126538] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[ 0.126591] ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.126640] ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.126697] ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.126753] ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[ 0.126812] ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[ 0.126889] ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0
[ 0.126950] ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0
[ 0.127010] ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0
[ 0.127070] ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0
[ 0.127110] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
[ 0.127183] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0
[ 0.127250] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0
[ 0.127316] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
[ 0.127382] ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22 23) *0, disabled.
[ 0.127449] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0
[ 0.127515] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0
[ 0.127581] ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0
[ 0.127647] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0
[ 0.127713] ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22 23) *0, disabled.
[ 0.127780] ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22 23) *0, disabled.
[ 0.127847] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
[ 0.127919] ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0
[ 0.127991] ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0
[ 0.128144] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.128148] vgaarb: loaded
[ 0.128149] vgaarb: bridge control possible 0000:01:00.0
[ 0.128204] PCI: Using ACPI for IRQ routing
[ 0.128208] PCI: pci_cache_line_size set to 64 bytes
[ 0.128221] pci 0000:00:00.0: address space collision: [mem 0xe0000000-0xefffffff pref] conflicts with GART [mem 0xe0000000-0xefffffff]
[ 0.128280] e820: reserve RAM buffer [mem 0x0009c000-0x0009ffff]
[ 0.128283] e820: reserve RAM buffer [mem 0x5fff0000-0x5fffffff]
[ 0.128429] NetLabel: Initializing
[ 0.128430] NetLabel: domain hash size = 128
[ 0.128432] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.128453] NetLabel: unlabeled traffic allowed by default
[ 0.139353] pnp: PnP ACPI init
[ 0.139383] ACPI: bus type pnp registered
[ 0.139432] pnp 00:00: [io 0x4000-0x407f]
[ 0.139434] pnp 00:00: [io 0x4080-0x40ff]
[ 0.139437] pnp 00:00: [io 0x4400-0x447f]
[ 0.139439] pnp 00:00: [io 0x4480-0x44ff]
[ 0.139441] pnp 00:00: [io 0x4800-0x487f]
[ 0.139444] pnp 00:00: [io 0x4880-0x48ff]
[ 0.139550] system 00:00: [io 0x4000-0x407f] has been reserved
[ 0.139554] system 00:00: [io 0x4080-0x40ff] has been reserved
[ 0.139557] system 00:00: [io 0x4400-0x447f] has been reserved
[ 0.139560] system 00:00: [io 0x4480-0x44ff] has been reserved
[ 0.139563] system 00:00: [io 0x4800-0x487f] has been reserved
[ 0.139566] system 00:00: [io 0x4880-0x48ff] has been reserved
[ 0.139572] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.139776] pnp 00:01: [mem 0x0009e000-0x000a1fff]
[ 0.139779] pnp 00:01: [mem 0x000cec00-0x000cffff]
[ 0.139781] pnp 00:01: [mem 0x000f0000-0x000fbfff]
[ 0.139784] pnp 00:01: [mem 0x000fc000-0x000fffff]
[ 0.139786] pnp 00:01: [mem 0x5fff0000-0x5fffffff]
[ 0.139789] pnp 00:01: [mem 0xffff0000-0xffffffff]
[ 0.139792] pnp 00:01: [mem 0x00000000-0x0009ffff]
[ 0.139794] pnp 00:01: [mem 0x00100000-0x5ffeffff]
[ 0.139797] pnp 00:01: [mem 0xfec00000-0xfec00fff]
[ 0.139799] pnp 00:01: [mem 0xfee00000-0xfeefffff]
[ 0.139802] pnp 00:01: [mem 0xfefff000-0xfeffffff]
[ 0.139804] pnp 00:01: [mem 0xfff80000-0xfff80fff]
[ 0.139807] pnp 00:01: [mem 0xfff90000-0xfffbffff]
[ 0.139809] pnp 00:01: [mem 0xfffed000-0xfffeffff]
[ 0.139815] pnp 00:01: disabling [mem 0x0009e000-0x000a1fff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
[ 0.139819] pnp 00:01: disabling [mem 0x000cec00-0x000cffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
[ 0.139823] pnp 00:01: disabling [mem 0x000f0000-0x000fbfff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
[ 0.139827] pnp 00:01: disabling [mem 0x000fc000-0x000fffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
[ 0.139830] pnp 00:01: disabling [mem 0x00000000-0x0009ffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
[ 0.139834] pnp 00:01: disabling [mem 0x00100000-0x5ffeffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
[ 0.139885] system 00:01: [mem 0x5fff0000-0x5fffffff] could not be reserved
[ 0.139889] system 00:01: [mem 0xffff0000-0xffffffff] has been reserved
[ 0.139892] system 00:01: [mem 0xfec00000-0xfec00fff] could not be reserved
[ 0.139895] system 00:01: [mem 0xfee00000-0xfeefffff] has been reserved
[ 0.139898] system 00:01: [mem 0xfefff000-0xfeffffff] has been reserved
[ 0.139902] system 00:01: [mem 0xfff80000-0xfff80fff] has been reserved
[ 0.139905] system 00:01: [mem 0xfff90000-0xfffbffff] has been reserved
[ 0.139908] system 00:01: [mem 0xfffed000-0xfffeffff] has been reserved
[ 0.139912] system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.139976] pnp 00:02: [bus 00-ff]
[ 0.140003] pnp 00:02: [io 0x0cf8-0x0cff]
[ 0.140006] pnp 00:02: [io 0x0cf0-0x0cf3]
[ 0.140009] pnp 00:02: [io 0x0000-0x0cf7 window]
[ 0.140011] pnp 00:02: [io 0x0d00-0xffff window]
[ 0.140014] pnp 00:02: [mem 0x000a0000-0x000bffff window]
[ 0.140017] pnp 00:02: [mem 0x000c0000-0x000dffff window]
[ 0.140020] pnp 00:02: [mem 0x60000000-0xfebfffff window]
[ 0.140101] pnp 00:02: Plug and Play ACPI device, IDs PNP0a03 (active)
[ 0.140629] pnp 00:03: [io 0x0010-0x001f]
[ 0.140631] pnp 00:03: [io 0x0022-0x003f]
[ 0.140634] pnp 00:03: [io 0x0044-0x005f]
[ 0.140636] pnp 00:03: [io 0x0062-0x0063]
[ 0.140639] pnp 00:03: [io 0x0065-0x006f]
[ 0.140641] pnp 00:03: [io 0x0074-0x007f]
[ 0.140644] pnp 00:03: [io 0x0091-0x0093]
[ 0.140646] pnp 00:03: [io 0x00a2-0x00bf]
[ 0.140648] pnp 00:03: [io 0x00e0-0x00ef]
[ 0.140651] pnp 00:03: [io 0x0b78-0x0b7b]
[ 0.140653] pnp 00:03: [io 0x0f78-0x0f7b]
[ 0.140656] pnp 00:03: [io 0x0a78-0x0a7b]
[ 0.140658] pnp 00:03: [io 0x0e78-0x0e7b]
[ 0.140660] pnp 00:03: [io 0x0bbc-0x0bbf]
[ 0.140663] pnp 00:03: [io 0x0fbc-0x0fbf]
[ 0.140665] pnp 00:03: [io 0x04d0-0x04d1]
[ 0.140741] system 00:03: [io 0x0b78-0x0b7b] has been reserved
[ 0.140744] system 00:03: [io 0x0f78-0x0f7b] has been reserved
[ 0.140748] system 00:03: [io 0x0a78-0x0a7b] has been reserved
[ 0.140751] system 00:03: [io 0x0e78-0x0e7b] has been reserved
[ 0.140754] system 00:03: [io 0x0bbc-0x0bbf] has been reserved
[ 0.140757] system 00:03: [io 0x0fbc-0x0fbf] has been reserved
[ 0.140760] system 00:03: [io 0x04d0-0x04d1] has been reserved
[ 0.140763] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.140777] pnp 00:04: [dma 4]
[ 0.140780] pnp 00:04: [io 0x0000-0x000f]
[ 0.140782] pnp 00:04: [io 0x0080-0x0090]
[ 0.140785] pnp 00:04: [io 0x0094-0x009f]
[ 0.140787] pnp 00:04: [io 0x00c0-0x00df]
[ 0.140832] pnp 00:04: Plug and Play ACPI device, IDs PNP0200 (active)
[ 0.140844] pnp 00:05: [io 0x0070-0x0073]
[ 0.140862] pnp 00:05: [irq 8]
[ 0.140904] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.140914] pnp 00:06: [io 0x0061]
[ 0.140959] pnp 00:06: Plug and Play ACPI device, IDs PNP0800 (active)
[ 0.140969] pnp 00:07: [io 0x00f0-0x00ff]
[ 0.140976] pnp 00:07: [irq 13]
[ 0.141019] pnp 00:07: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 0.141243] pnp 00:08: [io 0x03f8-0x03ff]
[ 0.141251] pnp 00:08: [irq 4]
[ 0.141340] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
[ 0.141514] pnp 00:09: [io 0x02f8-0x02ff]
[ 0.141522] pnp 00:09: [irq 3]
[ 0.141596] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
[ 0.141881] pnp 00:0a: [io 0x0378-0x037f]
[ 0.141883] pnp 00:0a: [io 0x0778-0x077b]
[ 0.141890] pnp 00:0a: [irq 7]
[ 0.141960] pnp 00:0a: Plug and Play ACPI device, IDs PNP0400 (active)
[ 0.142046] pnp 00:0b: [io 0x0060]
[ 0.142049] pnp 00:0b: [io 0x0064]
[ 0.142055] pnp 00:0b: [irq 1]
[ 0.142106] pnp 00:0b: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
[ 0.142129] pnp: PnP ACPI: found 12 devices
[ 0.142131] ACPI: ACPI bus type pnp unregistered
[ 0.148689] Switching to clocksource acpi_pm
[ 0.148760] pci 0000:01:00.0: BAR 6: assigned [mem 0xfc000000-0xfc01ffff pref]
[ 0.148765] pci 0000:00:0b.0: PCI bridge to [bus 01-01]
[ 0.148769] pci 0000:00:0b.0: bridge window [io 0xa000-0xafff]
[ 0.148774] pci 0000:00:0b.0: bridge window [mem 0xfa000000-0xfcffffff]
[ 0.148778] pci 0000:00:0b.0: bridge window [mem 0xd0000000-0xdfffffff pref]
[ 0.148787] pci 0000:02:08.0: BAR 6: assigned [mem 0xfde00000-0xfde0ffff pref]
[ 0.148790] pci 0000:00:0e.0: PCI bridge to [bus 02-02]
[ 0.148793] pci 0000:00:0e.0: bridge window [io 0x9000-0x9fff]
[ 0.148796] pci 0000:00:0e.0: bridge window [mem 0xfdf00000-0xfdffffff]
[ 0.148799] pci 0000:00:0e.0: bridge window [mem 0xfde00000-0xfdefffff pref]
[ 0.148814] pci 0000:00:0e.0: setting latency timer to 64
[ 0.148818] pci_bus 0000:00: resource 4 [io 0x0000-0xffff]
[ 0.148821] pci_bus 0000:00: resource 5 [mem 0x000a0000-0x000bffff]
[ 0.148824] pci_bus 0000:00: resource 6 [mem 0x60000000-0xfcffffffff]
[ 0.148827] pci_bus 0000:01: resource 0 [io 0xa000-0xafff]
[ 0.148829] pci_bus 0000:01: resource 1 [mem 0xfa000000-0xfcffffff]
[ 0.148832] pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff pref]
[ 0.148835] pci_bus 0000:02: resource 0 [io 0x9000-0x9fff]
[ 0.148837] pci_bus 0000:02: resource 1 [mem 0xfdf00000-0xfdffffff]
[ 0.148840] pci_bus 0000:02: resource 2 [mem 0xfde00000-0xfdefffff pref]
[ 0.148906] NET: Registered protocol family 2
[ 0.149029] IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.149029] TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
[ 0.153406] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.154706] TCP: Hash tables configured (established 262144 bind 65536)
[ 0.154710] TCP: reno registered
[ 0.154724] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.154769] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.154934] NET: Registered protocol family 1
[ 0.155185] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23
[ 0.223475] ACPI: PCI Interrupt Link [APCG] enabled at IRQ 22
[ 0.290128] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
[ 0.290189] pci 0000:01:00.0: Boot video device
[ 0.290265] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
[ 0.290348] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[ 0.290425] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
[ 0.290445] PCI: CLS 32 bytes, default 64
[ 0.290526] Unpacking initramfs...
[ 0.372340] Freeing initrd memory: 2940k freed
[ 0.379476] agpgart-amd64 0000:00:00.0: AGP bridge [10de/00e1]
[ 0.379485] agpgart-amd64 0000:00:00.0: aperture size 4096 MB is not right, using settings from NB
[ 0.379493] agpgart-amd64 0000:00:00.0: setting up Nforce3 AGP
[ 0.388295] agpgart-amd64 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
[ 0.388742] audit: initializing netlink socket (disabled)
[ 0.388762] type=2000 audit(1346927638.386:1): initialized
[ 0.402840] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.405016] VFS: Disk quotas dquot_6.5.2
[ 0.405085] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.405228] msgmni has been set to 2998
[ 0.405471] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.405502] io scheduler noop registered
[ 0.405504] io scheduler deadline registered
[ 0.405574] io scheduler cfq registered (default)
[ 0.412567] vesafb: mode is 1280x1024x32, linelength=5120, pages=0
[ 0.412569] vesafb: scrolling: redraw
[ 0.412572] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.412814] vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90000900000, using 5120k, total 5120k
[ 0.475467] Console: switching to colour frame buffer device 160x64
[ 0.537946] fb0: VESA VGA frame buffer device
[ 0.538002] GHES: HEST is not enabled!
[ 0.538068] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.558511] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.578950] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 0.599584] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.620075] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 0.620233] Linux agpgart interface v0.103
[ 0.620290] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 0.620292] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 0.620995] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.621096] mousedev: PS/2 mouse device common for all mice
[ 0.621204] rtc_cmos 00:05: RTC can wake from S4
[ 0.621333] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
[ 0.621357] rtc0: alarms up to one year, y3k, 242 bytes nvram
[ 0.621367] cpuidle: using governor ladder
[ 0.621370] cpuidle: using governor menu
[ 0.621586] drop_monitor: Initializing network drop monitor service
[ 0.621691] TCP: cubic registered
[ 0.621838] NET: Registered protocol family 10
[ 0.622084] NET: Registered protocol family 17
[ 0.622099] Key type dns_resolver registered
[ 0.622262] PM: Hibernation image not present or could not be loaded.
[ 0.622282] registered taskstats version 1
[ 0.622840] rtc_cmos 00:05: setting system clock to 2012-09-06 10:33:58 UTC (1346927638)
[ 0.624542] Freeing unused kernel memory: 756k freed
[ 0.625249] Write protecting the kernel read-only data: 8192k
[ 0.631386] Freeing unused kernel memory: 1496k freed
[ 0.635859] Freeing unused kernel memory: 616k freed
[ 0.647736] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 0.654805] systemd-udevd[38]: starting version 189
[ 0.730408] ACPI: bus type usb registered
[ 0.730453] usbcore: registered new interface driver usbfs
[ 0.730468] usbcore: registered new interface driver hub
[ 0.735252] usbcore: registered new device driver usb
[ 0.735879] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.739107] SCSI subsystem initialized
[ 0.746050] ehci_hcd 0000:00:02.2: setting latency timer to 64
[ 0.746058] ehci_hcd 0000:00:02.2: EHCI Host Controller
[ 0.746075] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
[ 0.746108] ehci_hcd 0000:00:02.2: debug port 1
[ 0.746114] ehci_hcd 0000:00:02.2: cache line size of 32 is not supported
[ 0.746141] ehci_hcd 0000:00:02.2: irq 21, io mem 0xfe02d000
[ 0.749031] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.750857] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.753402] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00
[ 0.753609] hub 1-0:1.0: USB hub found
[ 0.753616] hub 1-0:1.0: 8 ports detected
[ 0.753784] uhci_hcd 0000:02:09.0: UHCI Host Controller
[ 0.753793] uhci_hcd 0000:02:09.0: new USB bus registered, assigned bus number 2
[ 0.753839] uhci_hcd 0000:02:09.0: irq 19, io base 0x00009800
[ 0.753984] hub 2-0:1.0: USB hub found
[ 0.753989] hub 2-0:1.0: 2 ports detected
[ 0.754706] libata version 3.00 loaded.
[ 0.756811] ohci_hcd 0000:00:02.0: setting latency timer to 64
[ 0.756817] ohci_hcd 0000:00:02.0: OHCI Host Controller
[ 0.756829] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 3
[ 0.756869] ohci_hcd 0000:00:02.0: irq 23, io mem 0xfe02f000
[ 0.757452] uhci_hcd 0000:02:09.1: UHCI Host Controller
[ 0.757461] uhci_hcd 0000:02:09.1: new USB bus registered, assigned bus number 4
[ 0.757493] uhci_hcd 0000:02:09.1: irq 16, io base 0x00009400
[ 0.757704] hub 4-0:1.0: USB hub found
[ 0.757711] hub 4-0:1.0: 2 ports detected
[ 0.761428] ehci_hcd 0000:02:09.2: EHCI Host Controller
[ 0.761447] ehci_hcd 0000:02:09.2: new USB bus registered, assigned bus number 5
[ 0.761512] ehci_hcd 0000:02:09.2: irq 17, io mem 0xfdffe000
[ 0.770064] ehci_hcd 0000:02:09.2: USB 2.0 started, EHCI 1.00
[ 0.770287] hub 5-0:1.0: USB hub found
[ 0.770294] hub 5-0:1.0: 4 ports detected
[ 0.812239] hub 3-0:1.0: USB hub found
[ 0.812251] hub 3-0:1.0: 4 ports detected
[ 0.816572] ohci_hcd 0000:00:02.1: setting latency timer to 64
[ 0.816577] ohci_hcd 0000:00:02.1: OHCI Host Controller
[ 0.816589] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 6
[ 0.816630] ohci_hcd 0000:00:02.1: irq 22, io mem 0xfe02e000
[ 0.868954] hub 6-0:1.0: USB hub found
[ 0.868962] hub 6-0:1.0: 4 ports detected
[ 0.873501] sata_nv 0000:00:09.0: version 3.5
[ 0.873756] ACPI: PCI Interrupt Link [APSI] enabled at IRQ 20
[ 0.873833] sata_nv 0000:00:09.0: setting latency timer to 64
[ 0.874345] scsi0 : sata_nv
[ 0.874497] scsi1 : sata_nv
[ 0.874645] ata1: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xcc00 irq 20
[ 0.874648] ata2: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xcc08 irq 20
[ 0.878342] ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 23
[ 0.878391] sata_nv 0000:00:0a.0: setting latency timer to 64
[ 0.878840] scsi2 : sata_nv
[ 0.878963] scsi3 : sata_nv
[ 0.879110] ata3: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xb400 irq 23
[ 0.879112] ata4: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xb408 irq 23
[ 0.886479] pata_acpi 0000:00:08.0: power state changed by ACPI to D0
[ 0.886484] pata_acpi 0000:00:08.0: power state changed by ACPI to D0
[ 0.886533] pata_acpi 0000:00:08.0: setting latency timer to 64
[ 1.186695] ata1: SATA link down (SStatus 0 SControl 300)
[ 1.343364] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.350214] ata3.00: ATA-7: SAMSUNG SP1614C, SW100-34, max UDMA7
[ 1.350217] ata3.00: 312581808 sectors, multi 16: LBA48
[ 1.356871] ata3.00: configured for UDMA/133
[ 1.370024] usb 4-1: new low-speed USB device number 2 using uhci_hcd
[ 1.500024] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.500200] scsi 2:0:0:0: Direct-Access ATA SAMSUNG SP1614C SW10 PQ: 0 ANSI: 5
[ 1.966704] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.020180] ata4.00: ATA-8: WDC WD15EARS-00Z5B1, 80.00A80, max UDMA/133
[ 2.020183] ata4.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 2.033588] ata4.00: configured for UDMA/133
[ 2.033760] scsi 3:0:0:0: Direct-Access ATA WDC WD15EARS-00Z 80.0 PQ: 0 ANSI: 5
[ 2.036921] pata_amd 0000:00:08.0: version 0.4.1
[ 2.036948] pata_amd 0000:00:08.0: power state changed by ACPI to D0
[ 2.036952] pata_amd 0000:00:08.0: power state changed by ACPI to D0
[ 2.037017] pata_amd 0000:00:08.0: setting latency timer to 64
[ 2.040074] scsi4 : pata_amd
[ 2.041581] sd 2:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[ 2.041663] sd 2:0:0:0: [sda] Write Protect is off
[ 2.041667] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.041692] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.042020] scsi5 : pata_amd
[ 2.042592] ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xe000 irq 14
[ 2.042595] ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xe008 irq 15
[ 2.042887] sd 3:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
[ 2.042937] sd 3:0:0:0: [sdb] Write Protect is off
[ 2.042941] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 2.042964] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.055764] sdb: sdb1
[ 2.056082] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 2.056117] usbcore: registered new interface driver usbhid
[ 2.056119] usbhid: USB HID core driver
[ 2.073368] sda: sda1 sda2 sda3 sda4
[ 2.073827] sd 2:0:0:0: [sda] Attached SCSI disk
[ 2.200466] ata5.00: ATA-6: ST340810A, 3.39, max UDMA/100
[ 2.200473] ata5.00: 78165360 sectors, multi 16: LBA
[ 2.200484] ata5: nv_mode_filter: 0x3f39f&0x739f->0x739f, BIOS=0x7000 (0xc000c000) ACPI=0x701f (60:120:0x1b)
[ 2.213741] ata5.00: configured for UDMA/33
[ 2.213893] scsi 4:0:0:0: Direct-Access ATA ST340810A 3.39 PQ: 0 ANSI: 5
[ 2.214133] sd 4:0:0:0: [sdc] 78165360 512-byte logical blocks: (40.0 GB/37.2 GiB)
[ 2.214189] sd 4:0:0:0: [sdc] Write Protect is off
[ 2.214193] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 2.214216] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.244630] sdc: sdc1
[ 2.244919] sd 4:0:0:0: [sdc] Attached SCSI disk
[ 2.373623] ata6.00: ATAPI: _NEC DVD_RW ND-3540A, 1.01, max UDMA/33
[ 2.373634] ata6: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc000c000) ACPI=0x701f (60:120:0x1b)
[ 2.386892] ata6.00: configured for UDMA/33
[ 2.388189] scsi 5:0:0:0: CD-ROM _NEC DVD_RW ND-3540A 1.01 PQ: 0 ANSI: 5
[ 2.391609] input: OM as /devices/pci0000:00/0000:00:0e.0/0000:02:09.1/usb4/4-1/4-1:1.0/input/input1
[ 2.393267] hid-generic 0003:04F3:0234.0001: input,hidraw0: USB HID v1.11 Mouse [OM] on usb-0000:02:09.1-1/input0
[ 2.397693] sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
[ 2.397702] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.397986] sr 5:0:0:0: Attached scsi CD-ROM sr0
[ 3.150376] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[ 3.949356] systemd[1]: Successfully opened /dev/kmsg for logging.
[ 3.949760] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with options cpuset.
[ 3.949905] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct.
[ 3.950054] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
[ 3.950167] systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices.
[ 3.953404] systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer.
[ 3.953500] systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls of type cgroup with options net_cls.
[ 3.953597] systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio.
[ 3.956761] systemd[1]: systemd 189 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ; arch)
[ 3.979310] systemd[1]: Your kernel apparently lacks built-in autofs4 support. Might be a good idea to compile it in. We'll now try to work around this by loading the module...
[ 4.144298] systemd[1]: Inserted module 'autofs4'
[ 4.152053] systemd[1]: Set hostname to <box>.
[ 4.157882] systemd[1]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd/system.
[ 4.157991] systemd[1]: Installed release agent.
[ 4.158142] systemd[1]: Created root group.
[ 4.158219] systemd[1]: Using notification socket @/org/freedesktop/systemd1/notify
[ 4.158401] systemd[1]: Successfully created private D-Bus server.
[ 4.184882] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-cryptsetup-generator as 114
[ 4.185117] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-system-update-generator as 115
[ 4.185365] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-getty-generator as 116
[ 4.185641] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-fstab-generator as 117
[ 4.255375] systemd[1]: /usr/lib/systemd/system-generators/systemd-cryptsetup-generator exited successfully.
[ 4.255400] systemd[1]: /usr/lib/systemd/system-generators/systemd-system-update-generator exited successfully.
[ 4.255408] systemd[1]: /usr/lib/systemd/system-generators/systemd-getty-generator exited successfully.
[ 4.255416] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited successfully.
[ 4.313459] systemd[1]: Looking for unit files in:
[ 4.313463] systemd[1]: /etc/systemd/system
[ 4.313465] systemd[1]: /run/systemd/generator
[ 4.313468] systemd[1]: /usr/lib/systemd/system
[ 4.313471] systemd[1]: Disabled SysV init scripts and rcN.d links support
[ 4.422041] systemd[1]: Failed to load configuration for syslog.service: No such file or directory
[ 4.495651] systemd[1]: Failed to load configuration for plymouth-start.service: No such file or directory
[ 4.564783] systemd[1]: Failed to load configuration for rc-local.service: No such file or directory
[ 4.564799] systemd[1]: Failed to load configuration for plymouth-quit-wait.service: No such file or directory
[ 4.709247] systemd[1]: Failed to load configuration for auditd.service: No such file or directory
[ 4.752803] systemd[1]: -.mount changed dead -> mounted
[ 4.752894] systemd[1]: Activating default unit: default.target
[ 4.752901] systemd[1]: Trying to enqueue job graphical.target/start/replace
[ 4.753079] systemd[1]: Installed new job graphical.target/start as 1
[ 4.753085] systemd[1]: Installed new job multi-user.target/start as 2
[ 4.753089] systemd[1]: Installed new job basic.target/start as 3
[ 4.753094] systemd[1]: Installed new job sysinit.target/start as 4
[ 4.753098] systemd[1]: Installed new job local-fs.target/start as 5
[ 4.753102] systemd[1]: Installed new job home-hasardeur-Ext.mount/start as 6
[ 4.753108] systemd[1]: Installed new job systemd-journald.socket/start as 7
[ 4.753112] systemd[1]: Installed new job systemd-fsck@dev-disk-by\x2duuid-1A54880F5487EBB7.service/start as 9
[ 4.753116] systemd[1]: Installed new job dev-disk-by\x2duuid-1A54880F5487EBB7.device/start as 10
[ 4.753138] systemd[1]: Installed new job local-fs-pre.target/start as 11
[ 4.753142] systemd[1]: Installed new job home-hasardeur-Space.mount/start as 14
[ 4.753147] systemd[1]: Installed new job systemd-fsck@dev-disk-by\x2duuid-72290182\x2d7429\x2d4fb3\x2da421\x2d1e3bdf21dda9.service/start as 15
[ 4.753151] systemd[1]: Installed new job dev-disk-by\x2duuid-72290182\x2d7429\x2d4fb3\x2da421\x2d1e3bdf21dda9.device/start as 16
[ 4.753161] systemd[1]: Installed new job tmp.mount/start as 17
[ 4.753164] systemd[1]: Installed new job systemd-fsck-root.service/start as 18
[ 4.753168] systemd[1]: Installed new job systemd-remount-fs.service/start as 19
[ 4.753172] systemd[1]: Installed new job swap.target/start as 20
[ 4.753176] systemd[1]: Installed new job dev-disk-by\x2duuid-b5f8685d\x2d2706\x2d44fc\x2d882d\x2d662cc23e7c07.swap/start as 21
[ 4.753181] systemd[1]: Installed new job dev-disk-by\x2duuid-b5f8685d\x2d2706\x2d44fc\x2d882d\x2d662cc23e7c07.device/start as 22
[ 4.753191] systemd[1]: Installed new job systemd-udevd.service/start as 23
[ 4.753195] systemd[1]: Installed new job systemd-udevd-control.socket/start as 24
[ 4.753198] systemd[1]: Installed new job systemd-udevd-kernel.socket/start as 25
[ 4.753202] systemd[1]: Installed new job dev-mqueue.mount/start as 26
[ 4.753206] systemd[1]: Installed new job sys-kernel-config.mount/start as 27
[ 4.753209] systemd[1]: Installed new job systemd-random-seed-load.service/start as 28
[ 4.753213] systemd[1]: Installed new job systemd-ask-password-console.path/start as 29
[ 4.753217] systemd[1]: Installed new job systemd-udev-trigger.service/start as 30
[ 4.753220] systemd[1]: Installed new job sys-kernel-debug.mount/start as 31
[ 4.753224] systemd[1]: Installed new job systemd-modules-load.service/start as 32
[ 4.753228] systemd[1]: Installed new job sys-fs-fuse-connections.mount/start as 33
[ 4.753231] systemd[1]: Installed new job proc-sys-fs-binfmt_misc.automount/start as 34
[ 4.753235] systemd[1]: Installed new job systemd-journald.service/start as 35
[ 4.753239] systemd[1]: Installed new job systemd-journal-flush.service/start as 36
[ 4.753242] systemd[1]: Installed new job dev-hugepages.mount/start as 37
[ 4.753246] systemd[1]: Installed new job systemd-tmpfiles-setup.service/start as 38
[ 4.753249] systemd[1]: Installed new job cryptsetup.target/start as 39
[ 4.753253] systemd[1]: Installed new job systemd-sysctl.service/start as 40
[ 4.753256] systemd[1]: Installed new job systemd-vconsole-setup.service/start as 41
[ 4.753260] systemd[1]: Installed new job systemd-binfmt.service/start as 42
[ 4.753263] systemd[1]: Installed new job sockets.target/start as 45
[ 4.753267] systemd[1]: Installed new job dbus.socket/start as 46
[ 4.753271] systemd[1]: Installed new job systemd-initctl.socket/start as 47
[ 4.753274] systemd[1]: Installed new job systemd-shutdownd.socket/start as 48
[ 4.753278] systemd[1]: Installed new job alsa-restore.service/start as 49
[ 4.753281] systemd[1]: Installed new job console-kit-log-system-start.service/start as 50
[ 4.753285] systemd[1]: Installed new job systemd-tmpfiles-clean.timer/start as 51
[ 4.753289] systemd[1]: Installed new job ntpd.service/start as 52
[ 4.753292] systemd[1]: Installed new job remote-fs.target/start as 53
[ 4.753296] systemd[1]: Installed new job netcfg.service/start as 54
[ 4.753299] systemd[1]: Installed new job network.target/start as 55
[ 4.753302] systemd[1]: Installed new job cronie.service/start as 56
[ 4.753306] systemd[1]: Installed new job getty.target/start as 57
[ 4.753309] systemd[1]: Installed new job [email protected]/start as 58
[ 4.753313] systemd[1]: Installed new job systemd-ask-password-wall.path/start as 59
[ 4.753316] systemd[1]: Installed new job dbus.service/start as 60
[ 4.753320] systemd[1]: Installed new job systemd-logind.service/start as 61
[ 4.753323] systemd[1]: Installed new job systemd-user-sessions.service/start as 62
[ 4.753327] systemd[1]: Installed new job systemd-update-utmp-runlevel.service/start as 63
[ 4.753331] systemd[1]: Installed new job lxdm.service/start as 66
[ 4.753365] systemd[1]: Enqueued job graphical.target/start as 1
[ 4.753380] systemd[1]: Loaded units and determined initial transaction in 594ms 940us.
[ 4.753507] systemd[1]: Got SIGCHLD for process 113 (switch_root)
[ 4.753580] systemd[1]: Child 113 died (code=exited, status=0/SUCCESS)
[ 4.753667] systemd[1]: systemd-ask-password-wall.path changed dead -> waiting
[ 4.753676] systemd[1]: Job systemd-ask-password-wall.path/start finished, result=done
[ 4.753692] systemd[1]: remote-fs.target changed dead -> active
[ 4.753700] systemd[1]: Job remote-fs.target/start finished, result=done
[ 4.753747] systemd[1]: systemd-shutdownd.socket changed dead -> listening
[ 4.753755] systemd[1]: Job systemd-shutdownd.socket/start finished, result=done
[ 4.753786] systemd[1]: systemd-initctl.socket changed dead -> listening
[ 4.753793] systemd[1]: Job systemd-initctl.socket/start finished, result=done
[ 4.753807] systemd[1]: cryptsetup.target changed dead -> active
[ 4.753815] systemd[1]: Job cryptsetup.target/start finished, result=done
[ 4.753875] systemd[1]: Autofs kernel version 1.0
[ 4.753969] systemd[1]: Autofs protocol version 5.2
[ 4.753979] systemd[1]: proc-sys-fs-binfmt_misc.automount changed dead -> waiting
[ 4.753987] systemd[1]: Job proc-sys-fs-binfmt_misc.automount/start finished, result=done
[ 4.754036] systemd[1]: systemd-ask-password-console.path changed dead -> waiting
[ 4.754044] systemd[1]: Job systemd-ask-password-console.path/start finished, result=done
[ 4.754155] systemd[1]: systemd-udevd-kernel.socket changed dead -> listening
[ 4.754164] systemd[1]: Job systemd-udevd-kernel.socket/start finished, result=done
[ 4.754246] systemd[1]: systemd-udevd-control.socket changed dead -> listening
[ 4.754254] systemd[1]: Job systemd-udevd-control.socket/start finished, result=done
[ 4.754341] systemd[1]: systemd-journald.socket changed dead -> listening
[ 4.754349] systemd[1]: Job systemd-journald.socket/start finished, result=done
[ 4.754375] systemd[1]: Starting of systemd-fsck-root.service requested but condition failed. Ignoring.
[ 4.754379] systemd[1]: Job systemd-fsck-root.service/start finished, result=done
[ 4.754453] systemd[1]: About to execute: /usr/lib/systemd/systemd-remount-fs
[ 4.758929] systemd[1]: Forked /usr/lib/systemd/systemd-remount-fs as 118
[ 4.759050] systemd[1]: systemd-remount-fs.service changed dead -> start
[ 4.759250] systemd[1]: About to execute: /usr/lib/systemd/systemd-udevd
[ 4.826866] systemd[1]: Forked /usr/lib/systemd/systemd-udevd as 120
[ 4.826993] systemd[1]: systemd-udevd.service changed dead -> start
[ 4.827101] systemd[1]: About to execute: /bin/mount mqueue /dev/mqueue -t mqueue
[ 4.828859] systemd[1]: Forked /bin/mount as 121
[ 4.828923] systemd[1]: dev-mqueue.mount changed dead -> mounting
[ 4.829234] systemd[1]: About to execute: /usr/bin/udevadm trigger --type=subsystems --action=add
[ 4.833375] systemd[1]: Forked /usr/bin/udevadm as 122
[ 4.833513] systemd[1]: systemd-udev-trigger.service changed dead -> start
[ 4.833594] systemd[1]: About to execute: /bin/mount debugfs /sys/kernel/debug -t debugfs
[ 4.834846] systemd[1]: Forked /bin/mount as 123
[ 4.834893] systemd[1]: sys-kernel-debug.mount changed dead -> mounting
[ 4.859660] systemd[1]: About to execute: /usr/lib/systemd/systemd-modules-load
[ 4.860937] systemd[1]: Forked /usr/lib/systemd/systemd-modules-load as 124
[ 4.861068] systemd[1]: systemd-modules-load.service changed dead -> start
[ 4.861180] systemd[1]: About to execute: /bin/mount hugetlbfs /dev/hugepages -t hugetlbfs
[ 4.863410] systemd[1]: Forked /bin/mount as 125
[ 4.863451] systemd[1]: dev-hugepages.mount changed dead -> mounting
[ 4.917003] systemd[1]: About to execute: /usr/lib/systemd/systemd-sysctl
[ 4.918344] systemd[1]: Forked /usr/lib/systemd/systemd-sysctl as 126
[ 4.918493] systemd[1]: systemd-sysctl.service changed dead -> start
[ 4.918602] systemd[1]: About to execute: /usr/lib/systemd/systemd-vconsole-setup
[ 4.920070] systemd[1]: Forked /usr/lib/systemd/systemd-vconsole-setup as 127
[ 4.920224] systemd[1]: systemd-vconsole-setup.service changed dead -> start
[ 4.926908] systemd[1]: Starting of systemd-binfmt.service requested but condition failed. Ignoring.
[ 4.926918] systemd[1]: Job systemd-binfmt.service/start finished, result=done
[ 4.927036] systemd[1]: About to execute: /usr/lib/systemd/systemd-journald
[ 4.928214] systemd[1]: Forked /usr/lib/systemd/systemd-journald as 128
[ 4.928417] systemd[1]: systemd-journald.service changed dead -> running
[ 4.928436] systemd[1]: Job systemd-journald.service/start finished, result=done
[ 4.928562] systemd[1]: Running GC...
[ 4.929089] systemd[1]: Received SIGCHLD from PID 116 (n/a).
[ 4.929352] systemd[1]: Incoming traffic on systemd-journald.socket
[ 4.929370] systemd[1]: systemd-journald.socket changed listening -> running
[ 4.957457] systemd[1]: Got notification message for unit systemd-udevd.service
[ 4.957468] systemd[1]: systemd-udevd.service: Got message
[ 4.957473] systemd[1]: systemd-udevd.service: got READY=1
[ 4.957551] systemd[1]: systemd-udevd.service changed start -> running
[ 4.957567] systemd[1]: Job systemd-udevd.service/start finished, result=done
[ 4.957642] systemd-udevd[120]: starting version 189
[ 5.064497] systemd[1]: Incoming traffic on systemd-udevd-kernel.socket
[ 5.064520] systemd[1]: systemd-udevd-kernel.socket changed listening -> running
[ 5.066198] systemd[1]: Received SIGCHLD from PID 122 (udevadm).
[ 5.066234] systemd[1]: Got SIGCHLD for process 122 (udevadm)
[ 5.066313] systemd[1]: Child 122 died (code=exited, status=0/SUCCESS)
[ 5.066317] systemd[1]: Child 122 belongs to systemd-udev-trigger.service
[ 5.066333] systemd[1]: systemd-udev-trigger.service: main process exited, code=exited, status=0
[ 5.066341] systemd[1]: systemd-udev-trigger.service running next main command for state start
[ 5.066359] systemd[1]: About to execute: /usr/bin/udevadm trigger --type=devices --action=add
[ 5.067931] systemd[1]: Forked /usr/bin/udevadm as 130
[ 5.083596] systemd[1]: Received SIGCHLD from PID 130 (udevadm).
[ 5.083638] systemd[1]: Got SIGCHLD for process 130 (udevadm)
[ 5.083717] systemd[1]: Child 130 died (code=exited, status=0/SUCCESS)
[ 5.083721] systemd[1]: Child 130 belongs to systemd-udev-trigger.service
[ 5.083737] systemd[1]: systemd-udev-trigger.service: main process exited, code=exited, status=0
[ 5.084106] systemd[1]: systemd-udev-trigger.service changed start -> exited
[ 5.084118] systemd[1]: Job systemd-udev-trigger.service/start finished, result=done
[ 5.088748] systemd[1]: Received SIGCHLD from PID 126 (systemd-sysctl).
[ 5.088779] systemd[1]: Got SIGCHLD for process 126 (systemd-sysctl)
[ 5.088852] systemd[1]: Child 126 died (code=exited, status=0/SUCCESS)
[ 5.088856] systemd[1]: Child 126 belongs to systemd-sysctl.service
[ 5.088873] systemd[1]: systemd-sysctl.service: main process exited, code=exited, status=0
[ 5.089199] systemd[1]: systemd-sysctl.service changed start -> exited
[ 5.089210] systemd[1]: Job systemd-sysctl.service/start finished, result=done
[ 5.336181] FS-Cache: Loaded
[ 5.379562] RPC: Registered named UNIX socket transport module.
[ 5.379567] RPC: Registered udp transport module.
[ 5.379569] RPC: Registered tcp transport module.
[ 5.379570] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 5.585237] NFS: Registering the id_resolver key type
[ 5.585264] Key type id_resolver registered
[ 5.585266] Key type id_legacy registered
[ 5.585278] FS-Cache: Netfs 'nfs' registered for caching
[ 5.586108] systemd[1]: Received SIGCHLD from PID 124 (systemd-modules).
[ 5.586146] systemd[1]: Got SIGCHLD for process 124 (systemd-modules)
[ 5.586225] systemd[1]: Child 124 died (code=exited, status=0/SUCCESS)
[ 5.586229] systemd[1]: Child 124 belongs to systemd-modules-load.service
[ 5.586250] systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=0
[ 5.586590] systemd[1]: systemd-modules-load.service changed start -> exited
[ 5.586605] systemd[1]: Job systemd-modules-load.service/start finished, result=done
[ 5.586717] systemd[1]: Starting of sys-kernel-config.mount requested but condition failed. Ignoring.
[ 5.586722] systemd[1]: Job sys-kernel-config.mount/start finished, result=done
[ 5.586742] systemd[1]: Starting of sys-fs-fuse-connections.mount requested but condition failed. Ignoring.
[ 5.586746] systemd[1]: Job sys-fs-fuse-connections.mount/start finished, result=done
[ 5.615412] systemd[1]: Accepted connection on private bus.
[ 5.725920] systemd-journald[128]: Successfully opened /dev/kmsg for logging.
[ 5.758577] systemd-journald[128]: Fixed max_use=75.1M max_size=9.3M min_size=64.0K keep_free=37.5M
[ 5.758646] systemd-journald[128]: Reserving 17095 entries in hash table.
[ 5.759414] systemd-journald[128]: Vacuuming...
[ 5.759466] systemd-journald[128]: Flushing /dev/kmsg...
[ 5.777632] systemd[1]: dev-hugepages.mount changed mounting -> mounting-done
[ 5.777647] systemd[1]: Job dev-hugepages.mount/start finished, result=done
[ 5.777687] systemd[1]: sys-kernel-debug.mount changed mounting -> mounting-done
[ 5.777694] systemd[1]: Job sys-kernel-debug.mount/start finished, result=done
[ 5.777716] systemd[1]: dev-mqueue.mount changed mounting -> mounting-done
[ 5.777724] systemd[1]: Job dev-mqueue.mount/start finished, result=done
[ 5.777819] systemd[1]: Received SIGCHLD from PID 125 (mount).
[ 5.777855] systemd[1]: Got SIGCHLD for process 121 (mount)
[ 5.777932] systemd[1]: Child 121 died (code=exited, status=0/SUCCESS)
[ 5.777935] systemd[1]: Child 121 belongs to dev-mqueue.mount
[ 5.777949] systemd[1]: dev-mqueue.mount mount process exited, code=exited status=0
[ 5.777962] systemd[1]: dev-mqueue.mount changed mounting-done -> mounted
[ 5.777998] systemd[1]: Got SIGCHLD for process 123 (mount)
[ 5.778052] systemd[1]: Child 123 died (code=exited, status=0/SUCCESS)
[ 5.778056] systemd[1]: Child 123 belongs to sys-kernel-debug.mount
[ 5.778064] systemd[1]: sys-kernel-debug.mount mount process exited, code=exited status=0
[ 5.778073] systemd[1]: sys-kernel-debug.mount changed mounting-done -> mounted
[ 5.778104] systemd[1]: Got SIGCHLD for process 125 (mount)
[ 5.778159] systemd[1]: Child 125 died (code=exited, status=0/SUCCESS)
[ 5.778163] systemd[1]: Child 125 belongs to dev-hugepages.mount
[ 5.778171] systemd[1]: dev-hugepages.mount mount process exited, code=exited status=0
[ 5.778179] systemd[1]: dev-hugepages.mount changed mounting-done -> mounted
[ 5.778270] systemd[1]: Accepted connection on private bus.
[ 5.778429] systemd[1]: Accepted connection on private bus.
[ 5.778509] systemd[1]: Accepted connection on private bus.
[ 5.779032] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 5.779152] systemd[1]: systemd-udev-trigger.service: cgroup is empty
[ 5.779481] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 5.779740] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 5.786928] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 5.790217] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 5.790280] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 5.790338] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 5.796880] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 5.807799] systemd-journald[128]: systemd-journald running as pid 128
[ 5.808306] systemd[1]: Got notification message for unit systemd-journald.service
[ 5.808312] systemd[1]: systemd-journald.service: Got message
[ 5.808318] systemd[1]: systemd-journald.service: got STATUS=Processing requests...
[ 6.246284] EXT4-fs (sda2): re-mounted. Opts: (null)
[ 6.247294] systemd[1]: Received SIGCHLD from PID 118 (systemd-remount).
[ 6.247328] systemd[1]: Got SIGCHLD for process 118 (systemd-remount)
[ 6.247396] systemd[1]: Child 118 died (code=exited, status=0/SUCCESS)
[ 6.247401] systemd[1]: Child 118 belongs to systemd-remount-fs.service
[ 6.247419] systemd[1]: systemd-remount-fs.service: main process exited, code=exited, status=0
[ 6.247721] systemd[1]: systemd-remount-fs.service changed start -> exited
[ 6.247733] systemd[1]: Job systemd-remount-fs.service/start finished, result=done
[ 6.247797] systemd[1]: local-fs-pre.target changed dead -> active
[ 6.247805] systemd[1]: Job local-fs-pre.target/start finished, result=done
[ 6.317889] systemd[1]: About to execute: /bin/mount tmpfs /tmp -t tmpfs -o nodev,nosuid
[ 6.319475] systemd[1]: Forked /bin/mount as 140
[ 6.319523] systemd[1]: tmp.mount changed dead -> mounting
[ 6.319680] systemd[1]: About to execute: /usr/lib/systemd/systemd-random-seed load
[ 6.323401] systemd[1]: Forked /usr/lib/systemd/systemd-random-seed as 141
[ 6.323546] systemd[1]: systemd-random-seed-load.service changed dead -> start
[ 6.347887] systemd[1]: tmp.mount changed mounting -> mounting-done
[ 6.347901] systemd[1]: Job tmp.mount/start finished, result=done
[ 6.348383] systemd[1]: Received SIGCHLD from PID 140 (mount).
[ 6.348417] systemd[1]: Got SIGCHLD for process 140 (mount)
[ 6.348489] systemd[1]: Child 140 died (code=exited, status=0/SUCCESS)
[ 6.348493] systemd[1]: Child 140 belongs to tmp.mount
[ 6.348504] systemd[1]: tmp.mount mount process exited, code=exited status=0
[ 6.348515] systemd[1]: tmp.mount changed mounting-done -> mounted
[ 6.349779] systemd[1]: Accepted connection on private bus.
[ 6.350675] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 6.351301] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 6.433691] systemd[1]: dev-ttyS2.device changed dead -> plugged
[ 6.433715] systemd[1]: sys-devices-platform-serial8250-tty-ttyS2.device changed dead -> plugged
[ 6.434762] systemd[1]: dev-ttyS3.device changed dead -> plugged
[ 6.434780] systemd[1]: sys-devices-platform-serial8250-tty-ttyS3.device changed dead -> plugged
[ 6.439475] systemd[1]: Received SIGCHLD from PID 141 (systemd-random-).
[ 6.439513] systemd[1]: Got SIGCHLD for process 141 (systemd-random-)
[ 6.439Should I file a bug report? If so, with Arch or upstream?
-
Disk Utility - No Drives & No Shutdown
I've upgraded a Power Mac G5 2ghz machine:
Original Config: 1.5 gig memory, 2 x 160 gb HD, Tiger OS.
New Config: 3.5 gig memory, 1 x 320 gb HD, 3 x 500 gb HD, 1 x Sonnet Tempo SATA PCI Expansion Card , 1 x Sonnet G5 Jive Internal SATA Mounting.
The 2 additional 500 gb Baracuda HDs are mounted in the Sonnet Jive Mounting,( connected to the PCI card in slot 3), and powered with the supplied cable and plug from the optical drive, as per the sonnet instructions. The 2 remaining HDs are in the original slots A & B in the G5. Total of 7 volumes on 4 drives - 2 on drive 1, 3 on drive 2, one each on Drives 3 & 4
Problem: Computer suddenly is unable to locate any discs with Disk Utility - just get a spinning wheel. Can force quit Disk Utility, but then computer fails to shutdown, again the dreaded spinning wheel. Only means of shut down is by FORCE QUITTING (holding power button in).
Went back to square one. Refitted 2 original HDs slots A & B - complete with the OS already on HD (Tiger). Removed PCI card and mounting kit plus extra drives.
Result - all systems working normally. Went through a test sequence on this and all subsequent modifications:
All disks verified by Disk Utility, Images on other disc accessed via Bridge & Photoshop, start up and shutdown times logged.
Then added PCI card, tested as above - OK
Then added 3rd drive via mounting kit, tested as above - OK
Then added 4th drive via mounting kit, tested as above - OK
Removed mounting kit, PCI card, all drives and installed one new drive with Leopard in G5 position A. (Partitioned into 2 volumes)
Tested as above - OK
Then added 2nd new disk with images, position B, tested as above - OK
Then added PCI card, tested as above - OK
Then added 3rd drive via mounting kit, tested as above - OK
Then added 4th drive via mounting kit, tested as above - OK
Used this set up with Bridge & CS2 for an hour or so without a problem. The I re- partitioned Disk 2 (500 gb Seagate Baracuda) into 3 volumes, but disk still empty of data.
Then went through my test sequence and SAME PROBLEM RECURRED - Disk Utility (which I'd just used to partition disk) was unable to locate ANY drives - just the spinning wheel again. Sure enough the G5 refused to shutdown, spinning wheel again. I FORCE QUIT and left it alone!
I've phoned Sonnet and the card is compatible, firm ware is updated. Computer recognizes all discs and memory, until this problem appears. It seems that something in the system may not like more than 5 volumes being present. Additionally when I did a Leopard re-installation it failed to complete and just stopped installing before the software installation was complete. When I switched from "Erase & Install" to "Update" on the install menu it went in OK. I've successfully installed using this Leopard disk on a Quad Pro, so I don't think it's corrupted.
I'm now at a loss as what to do next to find and cure the problem - any advice would be appreciated
Regards
Max DuttonBeing a new Mac Mini the system is attempting to create a Fusion Drive setup out of your SSD. Do you have dual drives in the system, the built-in one in addition to the new one you installed?
This is an issue with the new Mac Mini and iMac systems (see here: http://reviews.cnet.com/8301-13727_7-57584237-263/disk-utility-may-combine-custo m-drive-setups-on-some-macs/) as these systems ship with Fusion Drive setups and Disk Utility assumes this is the desired setup when you use it to "fix" the drives.
You can see that when you select "Internal Drive" the type is "Logical Volume Group." Since this group is greater than the 840GB, my guess is this is the combined space from your SSD and the built-in one.
To clear this issue, open the Terminal (from the Utilities menu in the OS X installer), and run the following command:
diskutil cs list
You will see a tree of information, with one grouping showing a UUID for the Logical Volume Group (the UUID will be a string of numbers and letters, separated by several dashes).
With this UUID, run the following command to destroy the logical volume group (you can try copying and pasting the UUID, though I"m not sure if the services in the Recovery HD partition support copy and paste--otherwise just type it in manually):
diskutil cs delete UUID
When finished, follow the instructions in the artifcle I linked to above to install OS X to an external drive (if available) and use Disk Utility there to fix and manage the drives, as opposed to the version in the Recovery HD partition. -
Automation Plugin: Problems with Shutdown/Quit on Mac
Hi,
I've created an automation plugin similiar to the listener-plugin example in the sdk and I'm poping up a modal dialog when receiving the shutdown message/call from photoshop. When I quit Photoshop, the dialog shows for about 1-2 secs then vanishes and photoshop crashes. On the other hand, on windows the shutdown process is halted until I dismiss the dialog by button, just as I expected from a modal dialog (and then photoshop exits normaly).
I also tried to receive the eventQuit notification, put this event never ever seems to be sent by the host (both on win & mac).
Any help would be greatly appreciated!
Thanks,
MarcThanks Tom. I now use a mac os notification class to pop up my warning
message, this works fine. However I'm still lookin for a way to receive event notifications before photoshop has handled them, something like the PreTranslateMessage method from windows/mfc. Would that be possible?
Also, sometimes I miss some of the events, e.g. when closing a dirty document, photoshops asks if I want to save the doc, but I only receive the close-event, not the save-event. I noticed this seems to be the case with all events triggered indirectly, as the save event when closing a dirty doc or opening/closing/saving a doc from my auto-plugin.
So my big question is, am I doing it wrong or am I trying the impossible?
Thanks,
Marc -
Unable to restart/shutdown after upgrade
Hi all,
I recently upgraded my late 2010 macbook pro to mountain lion. Everything went well and the system is working fine. However, when I try to restart from the apple menu, nothing happens. Clicking About this Mac, Force Quit, Sleep, Restart..., Shut Down..., or Log Out do nothing. I tried the keyboard shortcuts for Force Quit and Sleep, Restart, and Shutdown but nothing happens either.
I made a time machine backup and put mountain lion on a USB to try a clean instal. But when I was in the installer and trying to erase the startup disk, the disk would not unmount and therefore not erase.
Everything else about the mac seems totally fine so far. The only thing is that by shuting it off with the power button, none of my system preferences are saved. The only other thing that might be of note was that after mountain lion was first installed, spotlight did not seem to be indexing, it was already completely indexed.
Has anyone else experienced this or know some possible solutions to this?
Any help is greatly appreciated.I found an answer in this thread (https://discussions.apple.com/thread/4139786?start=0&tstart=0), I had to restart twice (with "sudo restart" in Terminal) after deleting ~/Library/Preferences/com.apple.dock.plist ~/Library/Preferences/com.apple.dock.db First time, screen went grey while mouse still movable so used power button. Second time moved .plst to desktop then sudo restarted and everything worked as it should.
-
Unable to shutdown DB - Only ABORT works
Hi,
I just cloned a DB onto a Solaris 5 box with Oracle 7.3.4 from an AIX.
There were only a few transactions done by 1 user which probably had some sorting ; which used the temp tablespace probably.
When I tried to shutdown the DB - It wont ; I waited for 3 hours and tried an ABORT / Startup / Shutdown immediate. Still hangs for a long time. 2 hours and waiting.
Alert Log shows -- Waiting for smon to disable tx recovery.
I increased the "nice" priority for SMON thinking maybe it may help; but cant see any diff as of now.
I am thinking of leaving it for another few more hours to see if it would shutdown "immediate".
I read a few metalink notes : 1076161.6 / 61997.1 ; but the fet$ count sticks at a value and doesnt increase ( as per the document )
If this doesn't shut down in another 6 hours, will a constant "shu abort" cause any issues to the data ? I cant leave it for more than this time for it to shutdown gracefully.
Any Advice please ?
Thank you.Abort for the shutdown won't create as such any severe issue(s) for the db with the only impact that the next time, database would be requiring recovery to be done and this can take from no time to very significant time even , depending on the number of transactions happened in the last life of the database. Before doing an abort, if you really have to do so, issue an "alter system checkpoint" . This would ensure that the buffers from the cache is flushed to the datafile and on next startup, number of buffers requiring recovery should be less.
That said, a quick search over Google, gave this thread for the same error. Check it out and hope it helps.
http://www.orafaq.com/maillist/oracle-l/2000/06/21/0140.htm
HTH
Aman.... -
Using a Flat Panel iMac with 10.4.11 installed (can't install Leopard) and now am unable to Shut down or restart. Desktop clears, dock goes away but the background image stays, and the unit never shuts down. The pointer is movable during all this.
On another Topic list someone suggested deleting Bezelservices.plist from Prefs for the same issue. Tried that, didn't help.
After the unit is hard shut down and restarted, the startup takes a long time but eventually comes up and the OS seems to work OK. I've tried repairing permissions, using DiskWarrior to rebuild the directory. Still can't shut down. The problem persists regardless of the account I am in (admin or other).
Any ideas?
RobTry this.
Do a Find/Search using "loginwindow". The following files should appear:
com.apple.loginwindowlist.plist
loginwindowlist.plist
Trash the com.apple.loginwindowlist.plist file(s) (there may be more than one file with this name) & Shutdown using the Power button. Then startup & see if Shutdown or Restart works.
Cheers, Tom
Maybe you are looking for
-
I have a apple ipod touch but recently I restored all the settings, as well as the applications. But now I am not able to add songs to it. There is blank screen that shows the symbol like to connect to itunes first. I'm not able to use that... Please
-
I was a Sprint customer but sick of Commodore 64 dialup modem speeds so decided to switch to Verizon when the 5S came out. The map shows great coverage in my area, but to be sure I chatted with CSR and they confirmed I am good. I woke up at 3am on re
-
I can't get Itunes to load on my new Samsung Ultrabook?
HI, I have just bought a new Samsung Ultrabook, and was told ITunes would work on this computer. However, when I go to download it (I'm using Windows 7 and Internet Explorer 10 or Mozilla Firefox), the pop up window to download never appears - the we
-
How to keep icons displayed on bottom of screen
one to keep icons displayed on bottom of screen to make switching between programs easier
-
Lightroom 4.4 very slow - tried everything
Hi all... Lightroom 4.4 is very slow for me... everything takes longer than it should and it's driving me nuts. Can anyone help? Some details: I have LR 4.4 on a Macbook Air. I have two libraries: Internal - 5,000 photos External Drive - 21,000 photo