Motion New Install Crashes Loading a Template
I just loaded FCP Studio 5 on a new G5 quad 2.5 gig machine with 2 gig of ram and an Nvidia GForce 6600 graphics card.
I am working my way through the tutorials when I tried to load a Motion template as instructed. The system crashes.
I have the latest FCP updates and the Motion version is 2.1.2
I have tried loading other templates and some load and others make the system crash. Any thoughts?
Thanks
When you crash, you get the option of Reporting to Apple? Take that and copy this section of the log:
Command: Final Cut Pro
Path: /Applications/Final Cut Pro HD.app/Contents/MacOS/Final Cut Pro
Parent: WindowServer [117]
Version: 5.1 (5.1)
Build Version: 4
Project Name: FCPApp
Source Version: 602161028
PID: 1460
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000004
Thread 0 Crashed:
0 ...lCutPro.Plugins.QTRtEffects 0x061eea90 KGSetQTRtResFile(unsigned char, short*) + 72
1 ...lCutPro.Plugins.QTRtEffects 0x061f5b08 RTEffectComponentRegister() + 96
2 ...lCutPro.Plugins.QTRtEffects 0x061e521c PluginStart + 2028
3 com.apple.FinalCutPro 0x001b23e0 DispatchRegisterMessage(void*, void*) + 104
. - buncha info -
25 com.apple.FinalCutPro 0x002c10a8 main + 64
26 com.apple.FinalCutPro 0x00002c24 _start + 340
27 com.apple.FinalCutPro 0x00002acc start + 60
Thread 1:
0 libSystem.B.dylib 0x9002c128 semaphorewait_signaltrap + 8
That's the kinda thing we need...But only the crashed section, not the entire log - like the example above
Patrick
Similar Messages
-
Encore CS5.5 New Install crashes when I assign a drive to the project - Win7
Encore CS5.5 open fine but when I have assigned a drive and named the project then enter, it crashes with this error:
"Microsoft C+++
Runtime error
Program: C:\Pr....
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Then when I chose OK it says "the application has stopped running and Windows will search for a solution" of course it can't find one and so it closes the program.
This is a new install and the first time I've tried to run Encore on this new computer.
I've been editing in Premiere and exporting out thorugh AME just fine, but now I need to make a DVD and Encore won't stay open because of this error.
I've tried opening to another drive beside the raid but I get the same error.
I also have a Matrox MO2 aqttached but that doesn't seem to be a problem with Premiere either.
Can you help?
This is Win7 on an Asus P9X79 MB with Intell i73930 and 16 gigs of ram.>This is a new install and the first time I've tried to run Encore
Have you checked to see if there are any updates for Encore?
All Adobe updates start here and select product, read to see if you need to install updates in number order, or if the updates are cumulative for the individual product http://www.adobe.com/downloads/updates/
Have you also made sure Win7 is updated?
And, some other things to check...
As well as the below, right click the Encore icon and select Run as Administrator, which is NOT the same thing as running the computer with the Administrator account, and which fixes several "odd" problems... To create a two layer DVD (or a BluRay?), you MUST have Encore set to use the Run as Administrator option
Run as Administrator http://forums.adobe.com/thread/771202
-Set to always "run as" via icon http://forums.adobe.com/thread/969395
Odd Errors http://forums.adobe.com/thread/670174
Long File Names or odd characters cause problems
Read http://forums.adobe.com/thread/588273
And #4 http://forums.adobe.com/thread/666558
And This Message Thread http://forums.adobe.com/thread/665641 -
New install crashes at "initailizing files"
I have a new computer (Acer w/ Vista) that refuses to run
Dreamweaver. I initially installed the CS3 Suite - all programs ran
just fine except Dreamweaver. It would begin, but crash at
"initailizing files". It did this from the very first time I tried
to open it. I have since moved the Suite to another computer. Now
its a few months later and again I tried downloading the
Dreamweaver CS3 trial and I get the same result. I have read where
others had a similar problem when a website file hit some magic
file size. But this is a new installation that has never run. Any
ideas out there??> If enough people say something they will give Windows
users
> another patch before CS4 especially since it is supposed
to work with
> Vista.
I seriously doubt that this would happen.
The right way to deal with this problem is to submit a
support ticket as you
suggest. On windows the crash logs are saved on the desktop.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"SnakEyez02" <[email protected]> wrote in
message
news:g6tcmo$rtr$[email protected]..
> This seems to be happening to a lot of people lately.
Click on the "Your
> Account" link at the top of the page here and submit a
support ticket.
> They
> will probably ask for your log, but I honestly forget
where they are on
> Windows
> (I use a Mac). If enough people say something they will
give Windows
> users
> another patch before CS4 especially since it is supposed
to work with
> Vista.
> -
New Install Crashing of Premiere Pro CC
I've read several posts on this topic and tried following the advice. Windows 7. 64 bit. Dell Precision M6600 with Intel Core i7 vPro. All drivers updated. Installed Premiere Pro CC twice. Still having a crash on startup problem with the follwing report:
Problem signature:
Problem Event Name: BEX64
Application Name: Adobe Premiere Pro.exe
Application Version: 7.2.2.33
Application Timestamp: 532c3999
Fault Module Name: amdocl64.dll
Fault Module Version: 2.4.595.10
Fault Module Timestamp: 4eefa829
Exception Offset: 0000000000361cc8
Exception Code: c0000417
Exception Data: 0000000000000000
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: f2ff
Additional Information 2: f2ffa275bed653201935179f6f7d7368
Additional Information 3: 5070
Additional Information 4: 5070e2023e911ec53dcc55cbe3ca5c17Hi Acx_gd,
See if this forum post helps you out: http://forums.adobe.com/message/5677425#5677425
Thanks,
Kevin -
Yesterday I installed motion 5. It crashes when creating a new project or opening a template or old project. It runs on macbook 2.1 intel core 2.16 GHz. Thanks or helpful hints.
It used to be in there (id 226635 is the last one with it); should I clean it up a bit and put it back with a bit more of a disclaimer?
-
Motion 1.1 crashes on start-up with my new mac pro
I just upgraded to the a Mac pro 3GHz Quad-Core and now my Motion (v1.1) crashes right after start-up. To be more specific it crashed right after the "welcome to motion" menu pops up. I tried a re-install, taking out the preferences, and receipts. but still no luck. Does Motion 1.1 even work with my new Mac???
Power Mac 3GHz Quad-Core 8gb ram Mac OS X (10.4.9)
log:Thread: Unknown
Exception: EXCBADACCESS (0x0001)
Codes: KERNINVALIDADDRESS (0x0001) at 0x30000010
Thread 0:
0 <<00000000>> 0x82ef6658 0 + -2098239912
Thread 1:
0 com.apple.motion 0xb822fa2b strchr + 72
1 com.apple.motion 0xb81cb43b pthreadcondwait + 3114
2 com.apple.motion 0xb8167612 catchexception_raise_stateidentity + 318
3 com.apple.motion 0xb8166b4e CallPPCFunctionAtAddressInt + 177088
4 com.apple.motion 0xb8166a45 CallPPCFunctionAtAddressInt + 176823
5 com.apple.motion 0xb8167710 catchexception_raise_stateidentity + 572
6 com.apple.motion 0xb8200bb4 pthread_create + 1124
Thread 2:
0 com.apple.motion 0xb8134280 spinlockwrapper + 91752
1 com.apple.motion 0xb814d2b8 CallPPCFunctionAtAddressInt + 72490
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 3:
0 com.apple.motion 0xb8134280 spinlockwrapper + 91752
1 com.apple.motion 0xb814d2b8 CallPPCFunctionAtAddressInt + 72490
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 4:
0 com.apple.motion 0xb8134280 spinlockwrapper + 91752
1 com.apple.motion 0xb814d2b8 CallPPCFunctionAtAddressInt + 72490
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 5:
0 com.apple.motion 0xb8134280 spinlockwrapper + 91752
1 com.apple.motion 0xb814d2b8 CallPPCFunctionAtAddressInt + 72490
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 6:
0 com.apple.motion 0xb8134280 spinlockwrapper + 91752
1 com.apple.motion 0xb814d2b8 CallPPCFunctionAtAddressInt + 72490
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 7:
0 com.apple.motion 0xb8134280 spinlockwrapper + 91752
1 com.apple.motion 0xb814d2b8 CallPPCFunctionAtAddressInt + 72490
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 8:
0 com.apple.motion 0xb8134280 spinlockwrapper + 91752
1 com.apple.motion 0xb814d2b8 CallPPCFunctionAtAddressInt + 72490
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 9:
0 com.apple.motion 0xb81342f2 spinlockwrapper + 91866
1 com.apple.motion 0xb814d490 CallPPCFunctionAtAddressInt + 72962
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 10:
0 com.apple.motion 0xb81342f2 spinlockwrapper + 91866
1 com.apple.motion 0xb814d490 CallPPCFunctionAtAddressInt + 72962
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 11:
0 com.apple.motion 0xb81342f2 spinlockwrapper + 91866
1 com.apple.motion 0xb814d490 CallPPCFunctionAtAddressInt + 72962
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260
Thread 12:
0 com.apple.motion 0xb81342f2 spinlockwrapper + 91866
1 com.apple.motion 0xb814d490 CallPPCFunctionAtAddressInt + 72962
2 com.apple.motion 0xb80c803c 0xb8000000 + 819260Correct! Motion v.2, in its initial edition was earlier to Intel processor Mac. There was a programme for all those that had these versions to upgrade to v. 2.1 that is capable to run on Intel processors called "crossgrade" but it has expired. I think only the present version -3 included in FCS2- is available for sale. Evenmore versions prior to 2.1 can't work under Rosetta, so the only option is this...
-
Intermittent crashes on new install
Hi,
I am seeing intermittent crashes on a new install of Arch.
I see different messages on crash, quite often
INFO: rcu_preempt_state detected stalls on CPUs/tasks:
also
BUG: Bad page map in process bash
and other processes.
sometimes:
CPU: 1 PID: 1 Comm: shutdown tainted
I am vague here in the specific messages because it's not always the same and partly because I usually lose the logs due to hard restarting the machine.
I realize that the information here is somewhat lacking so I don't expect a magic answer to solve the problem. I am looking for advice on where to go from here to try and get it fixed.
The system seems normal most of the time then crashes without warning. When it does happen it will almost certainly get stuck at what seems to be the very last stage of shutdown (that is if it allowed me to use the shell). It might or might not go wrong after reboot then.
I've done 2 cycles of test using memtest, both passing.
Any advice? Could a faulty hard drive possible be the cause?TheSaint wrote:How much big is your RAM and swap ?
Perhaps you may add one more swap file, for testing purposes.
I suspect the most problem starts within swapping. You may look at this for references.
I've 4GB RAM and another 4GB swap partition.
I've tried using swapfile instead of the partition already to no avail.
I've also played with the swap performance settings, again, to no avail.
I've some more information to add now:
I left the system on last night and using it normally to see whether the hard drive replacement actually fixed the crashes (assuming the swap issues were separate). After 24 hours and some fair use, I was optimistic that the drive was in fact at fault. I then made some changes to a smb.conf file and restarted using:
sudo systemctl restart smbd.service
The systemd returned with an error saying smbd failed to start. I checked the logs and smbd reported a segfault. I try again several times, leave it a few minutes and try again (having reverted to the last working smb.conf), segfault still occurs. I then checked "free -m" and noticed that the memory is mostly unused but the entire RAM is used for cache (which I guess is normal anyway). I then cleared the cache:
echo 3 | tee /proc/sys/vm/drop_caches
and immediately I was able to restart smbd.
A few hours go by and I do some rsync'ing to a CIFS mounted share. Partway through I get the following:
Jan 15 18:17:01 engserv sudo[7859]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/rsync --info=PROGRESS2 -a /mnt/smb/pc1/Proj/All/ /media/data/Proj/All/
Jan 15 18:17:01 engserv sudo[7859]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
Jan 15 18:36:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
Jan 15 18:36:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:36:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:36:01 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
Jan 15 18:36:01 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
Jan 15 18:36:01 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
Jan 15 18:36:01 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
Jan 15 18:36:01 engserv kernel: Call Trace:
Jan 15 18:36:01 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
Jan 15 18:36:01 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
Jan 15 18:36:01 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
Jan 15 18:36:01 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
Jan 15 18:36:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:36:01 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
Jan 15 18:36:01 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
Jan 15 18:36:01 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
Jan 15 18:36:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:36:01 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
Jan 15 18:36:01 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
Jan 15 18:36:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:36:01 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
Jan 15 18:36:01 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
Jan 15 18:36:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:36:01 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
Jan 15 18:36:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:36:01 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
Jan 15 18:36:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:36:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:36:01 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
Jan 15 18:36:01 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
Jan 15 18:36:01 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
Jan 15 18:36:01 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
Jan 15 18:36:01 engserv kernel: Call Trace:
Jan 15 18:36:01 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
Jan 15 18:36:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:36:01 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
Jan 15 18:36:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:36:01 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
Jan 15 18:36:01 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
Jan 15 18:36:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
Jan 15 18:36:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
Jan 15 18:36:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:36:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
Jan 15 18:36:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:36:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
Jan 15 18:36:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
Jan 15 18:36:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
Jan 15 18:36:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
Jan 15 18:36:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
Jan 15 18:36:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
Jan 15 18:36:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
Jan 15 18:36:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
Jan 15 18:36:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
Jan 15 18:36:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
Jan 15 18:38:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
Jan 15 18:38:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:38:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:38:00 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
Jan 15 18:38:00 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
Jan 15 18:38:00 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
Jan 15 18:38:00 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
Jan 15 18:38:00 engserv kernel: Call Trace:
Jan 15 18:38:00 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
Jan 15 18:38:00 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
Jan 15 18:38:00 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
Jan 15 18:38:00 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
Jan 15 18:38:00 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:38:00 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
Jan 15 18:38:00 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
Jan 15 18:38:00 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
Jan 15 18:38:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:38:00 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
Jan 15 18:38:00 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
Jan 15 18:38:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:38:00 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
Jan 15 18:38:00 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
Jan 15 18:38:00 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:38:00 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
Jan 15 18:38:00 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:38:00 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
Jan 15 18:38:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:38:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:38:00 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
Jan 15 18:38:00 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
Jan 15 18:38:00 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
Jan 15 18:38:00 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
Jan 15 18:38:00 engserv kernel: Call Trace:
Jan 15 18:38:00 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
Jan 15 18:38:00 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:38:00 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
Jan 15 18:38:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:38:00 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
Jan 15 18:38:00 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
Jan 15 18:38:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
Jan 15 18:38:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
Jan 15 18:38:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:38:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
Jan 15 18:38:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:38:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
Jan 15 18:38:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
Jan 15 18:38:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
Jan 15 18:38:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
Jan 15 18:38:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
Jan 15 18:38:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
Jan 15 18:38:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
Jan 15 18:38:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
Jan 15 18:38:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
Jan 15 18:38:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
Jan 15 18:40:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
Jan 15 18:40:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:40:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:40:00 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
Jan 15 18:40:00 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
Jan 15 18:40:00 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
Jan 15 18:40:00 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
Jan 15 18:40:00 engserv kernel: Call Trace:
Jan 15 18:40:00 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
Jan 15 18:40:00 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
Jan 15 18:40:00 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
Jan 15 18:40:00 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
Jan 15 18:40:00 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:40:00 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
Jan 15 18:40:00 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
Jan 15 18:40:01 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
Jan 15 18:40:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:40:01 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
Jan 15 18:40:01 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
Jan 15 18:40:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:40:01 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
Jan 15 18:40:01 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
Jan 15 18:40:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:40:01 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
Jan 15 18:40:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:40:01 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
Jan 15 18:40:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:40:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:40:01 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
Jan 15 18:40:01 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
Jan 15 18:40:01 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
Jan 15 18:40:01 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
Jan 15 18:40:01 engserv kernel: Call Trace:
Jan 15 18:40:01 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
Jan 15 18:40:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:40:01 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
Jan 15 18:40:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:40:01 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
Jan 15 18:40:01 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
Jan 15 18:40:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
Jan 15 18:40:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
Jan 15 18:40:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:40:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
Jan 15 18:40:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:40:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
Jan 15 18:40:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
Jan 15 18:40:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
Jan 15 18:40:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
Jan 15 18:40:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
Jan 15 18:40:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
Jan 15 18:40:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
Jan 15 18:40:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
Jan 15 18:40:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
Jan 15 18:40:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
Jan 15 18:42:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
Jan 15 18:42:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:42:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:42:01 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
Jan 15 18:42:01 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
Jan 15 18:42:01 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
Jan 15 18:42:01 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
Jan 15 18:42:01 engserv kernel: Call Trace:
Jan 15 18:42:01 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
Jan 15 18:42:01 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
Jan 15 18:42:01 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
Jan 15 18:42:01 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
Jan 15 18:42:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:42:01 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
Jan 15 18:42:01 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
Jan 15 18:42:01 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
Jan 15 18:42:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:42:01 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
Jan 15 18:42:01 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
Jan 15 18:42:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:42:01 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
Jan 15 18:42:01 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
Jan 15 18:42:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:42:01 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
Jan 15 18:42:01 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:42:01 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
Jan 15 18:42:01 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:42:01 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:42:01 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
Jan 15 18:42:01 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
Jan 15 18:42:01 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
Jan 15 18:42:01 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
Jan 15 18:42:01 engserv kernel: Call Trace:
Jan 15 18:42:01 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
Jan 15 18:42:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:42:01 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
Jan 15 18:42:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:42:01 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
Jan 15 18:42:01 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
Jan 15 18:42:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
Jan 15 18:42:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
Jan 15 18:42:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:42:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
Jan 15 18:42:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:42:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
Jan 15 18:42:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
Jan 15 18:42:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
Jan 15 18:42:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
Jan 15 18:42:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
Jan 15 18:42:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
Jan 15 18:42:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
Jan 15 18:42:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
Jan 15 18:42:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
Jan 15 18:42:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
Jan 15 18:44:00 engserv kernel: INFO: task jbd2/sdb1-8:215 blocked for more than 120 seconds.
Jan 15 18:44:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:44:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:44:00 engserv kernel: jbd2/sdb1-8 D 0000000000000000 0 215 2 0x00000000
Jan 15 18:44:00 engserv kernel: ffff8800bcc27c90 0000000000000046 ffff8800bd24c670 00000000000135c0
Jan 15 18:44:00 engserv kernel: ffff8800bcc27fd8 00000000000135c0 ffff88003b934670 ffff8800bd24c670
Jan 15 18:44:00 engserv kernel: ffff8800bcc27be0 ffff8800bcc27bf8 ffff8800bcc27be0 ffffffffa024b3c7
Jan 15 18:44:00 engserv kernel: Call Trace:
Jan 15 18:44:00 engserv kernel: [<ffffffffa024b3c7>] ? ext4_mb_unload_buddy.isra.18+0x27/0x30 [ext4]
Jan 15 18:44:00 engserv kernel: [<ffffffff810b5f30>] ? cpuacct_charge+0x50/0x60
Jan 15 18:44:00 engserv kernel: [<ffffffff810a4c9c>] ? update_curr+0xec/0x1b0
Jan 15 18:44:00 engserv kernel: [<ffffffff810a51ff>] ? dequeue_entity+0x13f/0x580
Jan 15 18:44:00 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:44:00 engserv kernel: [<ffffffffa00fb806>] jbd2_journal_commit_transaction+0x236/0x19c0 [jbd2]
Jan 15 18:44:00 engserv kernel: [<ffffffff810a9954>] ? pick_next_task_fair+0x144/0x520
Jan 15 18:44:00 engserv kernel: [<ffffffff810136b2>] ? __switch_to+0x1b2/0x5e0
Jan 15 18:44:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:44:00 engserv kernel: [<ffffffff810d659e>] ? try_to_del_timer_sync+0x5e/0x90
Jan 15 18:44:00 engserv kernel: [<ffffffffa010280c>] kjournald2+0xec/0x2a0 [jbd2]
Jan 15 18:44:00 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:44:00 engserv kernel: [<ffffffffa0102720>] ? commit_timeout+0x10/0x10 [jbd2]
Jan 15 18:44:00 engserv kernel: [<ffffffff8108e2ea>] kthread+0xea/0x100
Jan 15 18:44:00 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:44:00 engserv kernel: [<ffffffff8153dbbc>] ret_from_fork+0x7c/0xb0
Jan 15 18:44:00 engserv kernel: [<ffffffff8108e200>] ? kthread_create_on_node+0x1b0/0x1b0
Jan 15 18:44:00 engserv kernel: INFO: task rsync:7862 blocked for more than 120 seconds.
Jan 15 18:44:00 engserv kernel: Not tainted 3.17.6-1-ARCH #1
Jan 15 18:44:00 engserv kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 15 18:44:00 engserv kernel: rsync D 0000000000000002 0 7862 7861 0x00000000
Jan 15 18:44:00 engserv kernel: ffff8800bd337a80 0000000000000086 ffff88003b934670 00000000000135c0
Jan 15 18:44:00 engserv kernel: ffff8800bd337fd8 00000000000135c0 ffff880138400000 ffff88003b934670
Jan 15 18:44:00 engserv kernel: ffffffff00000e00 00000000010200da 0000000000000246 ffff88013eff96c0
Jan 15 18:44:00 engserv kernel: Call Trace:
Jan 15 18:44:01 engserv kernel: [<ffffffff8115ab54>] ? __alloc_pages_nodemask+0x174/0xb40
Jan 15 18:44:01 engserv kernel: [<ffffffff81539649>] schedule+0x29/0x70
Jan 15 18:44:01 engserv kernel: [<ffffffffa00f808d>] wait_transaction_locked+0x8d/0xd0 [jbd2]
Jan 15 18:44:01 engserv kernel: [<ffffffff810af960>] ? __wake_up_sync+0x20/0x20
Jan 15 18:44:01 engserv kernel: [<ffffffffa00f83c2>] start_this_handle+0x262/0x610 [jbd2]
Jan 15 18:44:01 engserv kernel: [<ffffffff81150c1e>] ? __add_to_page_cache_locked+0x24e/0x2c0
Jan 15 18:44:01 engserv kernel: [<ffffffff811ab9da>] ? kmem_cache_alloc+0x16a/0x170
Jan 15 18:44:01 engserv kernel: [<ffffffffa00f8b6b>] jbd2__journal_start+0xfb/0x210 [jbd2]
Jan 15 18:44:01 engserv kernel: [<ffffffffa021ce4f>] ? ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:44:01 engserv kernel: [<ffffffffa02486cd>] __ext4_journal_start_sb+0x6d/0x110 [ext4]
Jan 15 18:44:01 engserv kernel: [<ffffffffa021ce4f>] ext4_da_write_begin+0x10f/0x350 [ext4]
Jan 15 18:44:01 engserv kernel: [<ffffffff8115191a>] generic_perform_write+0xca/0x1e0
Jan 15 18:44:01 engserv kernel: [<ffffffff81153345>] __generic_file_write_iter+0x1e5/0x3b0
Jan 15 18:44:01 engserv kernel: [<ffffffffa0211eba>] ext4_file_write_iter+0x11a/0x3f0 [ext4]
Jan 15 18:44:01 engserv kernel: [<ffffffff811dc05b>] ? core_sys_select+0x2cb/0x330
Jan 15 18:44:01 engserv kernel: [<ffffffff8142935b>] ? sock_aio_read.part.29+0xcb/0x100
Jan 15 18:44:01 engserv kernel: [<ffffffff811c71ee>] new_sync_write+0x8e/0xd0
Jan 15 18:44:01 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
Jan 15 18:44:01 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
Jan 15 18:44:01 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
Jan 15 18:44:01 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
Jan 15 18:48:48 engserv sudo[7897]: sth : TTY=tty1 ; PWD=/home/sth ; USER=root ; COMMAND=/usr/bin/journalctl -xb --no-pager
Jan 15 18:48:48 engserv sudo[7897]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
Jan 15 18:48:49 engserv sudo[7897]: pam_unix(sudo:session): session closed for user root
Jan 15 18:51:45 engserv sudo[7859]: pam_unix(sudo:session): session closed for user root
Jan 15 18:52:38 engserv sudo[7911]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/pkill rsync
Jan 15 18:52:38 engserv sudo[7911]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
Jan 15 18:52:38 engserv sudo[7911]: pam_unix(sudo:session): session closed for user root
Jan 15 18:52:50 engserv sudo[7916]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/pkill rsync
Jan 15 18:52:50 engserv sudo[7916]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
Jan 15 18:52:50 engserv sudo[7916]: pam_unix(sudo:session): session closed for user root
Jan 15 18:53:06 engserv sudo[7918]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/pkill -9 rsync
Jan 15 18:53:06 engserv sudo[7918]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
Jan 15 18:53:06 engserv sudo[7918]: pam_unix(sudo:session): session closed for user root
Jan 15 18:55:59 engserv sudo[7949]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/pkill -9 rsync
Jan 15 18:55:59 engserv sudo[7949]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
Jan 15 18:55:59 engserv sudo[7949]: pam_unix(sudo:session): session closed for user root
Jan 15 18:56:21 engserv systemd[1]: Starting Getty on tty2...
-- Subject: Unit [email protected] has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit [email protected] has begun starting up.
Jan 15 18:56:21 engserv systemd[1]: Started Getty on tty2.
-- Subject: Unit [email protected] has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit [email protected] has finished starting up.
-- The start-up result is done.
Jan 15 18:56:25 engserv login[7954]: pam_unix(login:session): session opened for user sth by LOGIN(uid=0)
Jan 15 18:56:25 engserv systemd[1]: Starting Session c4 of user sth.
-- Subject: Unit session-c4.scope has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c4.scope has begun starting up.
Jan 15 18:56:25 engserv systemd-logind[275]: New session c4 of user sth.
-- Subject: A new session c4 has been created for user sth
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
-- A new session with the ID c4 has been created for the user sth.
-- The leading process of the session is 7954.
Jan 15 18:56:25 engserv systemd[1]: Started Session c4 of user sth.
-- Subject: Unit session-c4.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c4.scope has finished starting up.
-- The start-up result is done.
Jan 15 18:56:25 engserv login[7954]: LOGIN ON tty2 BY sth
Jan 15 18:56:39 engserv sudo[7960]: sth : TTY=tty2 ; PWD=/home/sth ; USER=root ; COMMAND=/usr/bin/umount /media/data/
Jan 15 18:56:39 engserv sudo[7960]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
Jan 15 18:56:39 engserv sudo[7960]: pam_unix(sudo:session): session closed for user root
Jan 15 19:02:43 engserv sudo[7984]: sth : TTY=pts/0 ; PWD=/mnt/smb/share2 ; USER=root ; COMMAND=/usr/bin/tee /proc/sys/vm/drop_caches
Jan 15 19:02:43 engserv sudo[7984]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
Jan 15 19:02:43 engserv kernel: ------------[ cut here ]------------
Jan 15 19:02:43 engserv kernel: WARNING: CPU: 3 PID: 7985 at mm/truncate.c:508 invalidate_mapping_pages+0x1c1/0x1f0()
Jan 15 19:02:43 engserv kernel: Modules linked in: des3_ede_x86_64 des_generic arc4 ecb md4 md5 hmac nls_utf8 cifs dns_resolver fscache cfg80211 rfkill nls_iso8859_1 nls_cp437 vfat fat nouveau video ttm drm_kms_helper drm kvm_amd r8169 i2c_algo_bit kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel mxm_wmi evdev snd_hda_codec_realtek snd_hda_codec_hdmi sp5100_tco aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd mac_hid pcspkr serio_raw edac_core snd_hda_codec_generic edac_mce_amd mii fam15h_power i2c_piix4 k10temp hwmon i2c_core shpchp tpm_infineon snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore wmi tpm_tis tpm button acpi_cpufreq processor sch_fq_codel ext4 crc16 mbcache jbd2 sd_mod crc_t10dif crct10dif_common atkbd libps2 ahci firewire_ohci
Jan 15 19:02:43 engserv kernel: ehci_pci libahci ohci_pci firewire_core ohci_hcd libata crc_itu_t xhci_hcd ehci_hcd scsi_mod usbcore usb_common i8042 serio
Jan 15 19:02:43 engserv kernel: CPU: 3 PID: 7985 Comm: tee Not tainted 3.17.6-1-ARCH #1
Jan 15 19:02:43 engserv kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD3, BIOS FC 02/05/2013
Jan 15 19:02:43 engserv kernel: 0000000000000000 000000008e7f3f05 ffff8800b9727c58 ffffffff81537c3e
Jan 15 19:02:43 engserv kernel: 0000000000000000 ffff8800b9727c90 ffffffff8107079d 0000000000000003
Jan 15 19:02:43 engserv kernel: 0000000000000003 ffff880137e2c0a8 ffffffffffffffff ffffea0000637e00
Jan 15 19:02:43 engserv kernel: Call Trace:
Jan 15 19:02:43 engserv kernel: [<ffffffff81537c3e>] dump_stack+0x4d/0x6f
Jan 15 19:02:43 engserv kernel: [<ffffffff8107079d>] warn_slowpath_common+0x7d/0xa0
Jan 15 19:02:43 engserv kernel: [<ffffffff810708ca>] warn_slowpath_null+0x1a/0x20
Jan 15 19:02:43 engserv kernel: [<ffffffff811627c1>] invalidate_mapping_pages+0x1c1/0x1f0
Jan 15 19:02:43 engserv kernel: [<ffffffff81224e0c>] drop_pagecache_sb+0xac/0xf0
Jan 15 19:02:43 engserv kernel: [<ffffffff81224d60>] ? do_coredump+0xec0/0xec0
Jan 15 19:02:43 engserv kernel: [<ffffffff811cb432>] iterate_supers+0xb2/0x110
Jan 15 19:02:43 engserv kernel: [<ffffffff81224ed6>] drop_caches_sysctl_handler+0x86/0x140
Jan 15 19:02:43 engserv kernel: [<ffffffff81206dac>] ? fsnotify+0x28c/0x370
Jan 15 19:02:43 engserv kernel: [<ffffffff812387a3>] proc_sys_call_handler+0xd3/0xf0
Jan 15 19:02:43 engserv kernel: [<ffffffff812387d4>] proc_sys_write+0x14/0x20
Jan 15 19:02:43 engserv kernel: [<ffffffff811c7967>] vfs_write+0xb7/0x200
Jan 15 19:02:43 engserv kernel: [<ffffffff811c787c>] ? vfs_read+0x13c/0x170
Jan 15 19:02:43 engserv kernel: [<ffffffff811c85d9>] SyS_write+0x59/0xd0
Jan 15 19:02:43 engserv kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
Jan 15 19:02:43 engserv kernel: ---[ end trace 2601969f96a93148 ]---
Jan 15 19:02:44 engserv kernel: tee (7985): drop_caches: 3
Jan 15 19:08:04 engserv sudo[8011]: sth : TTY=tty2 ; PWD=/home/sth ; USER=root ; COMMAND=/usr/bin/reboot
Jan 15 19:08:04 engserv sudo[8011]: pam_unix(sudo:session): session opened for user root by sth(uid=0)
Jan 15 19:08:04 engserv systemd[1]: Unmounting /media/data...
-- Subject: Unit media-data.mount has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit media-data.mount has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Timers.
-- Subject: Unit timers.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit timers.target has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped target Timers.
-- Subject: Unit timers.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit timers.target has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Session c3 of user sth.
-- Subject: Unit session-c3.scope has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c3.scope has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped Session c3 of user sth.
-- Subject: Unit session-c3.scope has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c3.scope has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping system-systemd\x2dfsck.slice.
-- Subject: Unit system-systemd\x2dfsck.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit system-systemd\x2dfsck.slice has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Removed slice system-systemd\x2dfsck.slice.
-- Subject: Unit system-systemd\x2dfsck.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit system-systemd\x2dfsck.slice has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Sound Card.
-- Subject: Unit sound.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sound.target has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped target Sound Card.
-- Subject: Unit sound.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sound.target has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Deactivating swap Swap Partition...
-- Subject: Unit dev-sda3.swap has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-sda3.swap has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Graphical Interface.
-- Subject: Unit graphical.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit graphical.target has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped target Graphical Interface.
-- Subject: Unit graphical.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit graphical.target has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Deactivating swap Swap Partition...
-- Subject: Unit dev-sda3.swap has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-sda3.swap has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Daily Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.timer has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-clean.timer has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped Daily Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.timer has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-clean.timer has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Session c1 of user sth.
-- Subject: Unit session-c1.scope has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c1.scope has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped Session c1 of user sth.
-- Subject: Unit session-c1.scope has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c1.scope has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping User Manager for UID 1000...
-- Subject: Unit [email protected] has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit [email protected] has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
-- Subject: Unit avahi-daemon.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit avahi-daemon.service has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Deactivating swap Swap Partition...
-- Subject: Unit dev-sda3.swap has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-sda3.swap has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Session c4 of user sth.
-- Subject: Unit session-c4.scope has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c4.scope has begun shutting down.
Jan 15 19:08:04 engserv login[276]: pam_unix(login:session): session closed for user sth
Jan 15 19:08:04 engserv login[276]: pam_systemd(login:session): Failed to release session: Interrupted system call
Jan 15 19:08:04 engserv avahi-daemon[411]: Got SIGTERM, quitting.
Jan 15 19:08:04 engserv avahi-daemon[411]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 172.16.1.2.
Jan 15 19:08:04 engserv avahi-daemon[411]: avahi-daemon 0.6.31 exiting.
Jan 15 19:08:04 engserv sshd[359]: Received signal 15; terminating.
Jan 15 19:08:04 engserv systemd[1]: Stopped Session c4 of user sth.
-- Subject: Unit session-c4.scope has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit session-c4.scope has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Multi-User System.
-- Subject: Unit multi-user.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit multi-user.target has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped target Multi-User System.
-- Subject: Unit multi-user.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit multi-user.target has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Daily verification of password and group files.
-- Subject: Unit shadow.timer has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit shadow.timer has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped Daily verification of password and group files.
-- Subject: Unit shadow.timer has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit shadow.timer has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping D-Bus System Message Bus...
-- Subject: Unit dbus.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dbus.service has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Daily man-db cache update.
-- Subject: Unit man-db.timer has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit man-db.timer has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped Daily man-db cache update.
-- Subject: Unit man-db.timer has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit man-db.timer has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Login Prompts.
-- Subject: Unit getty.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit getty.target has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped target Login Prompts.
-- Subject: Unit getty.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit getty.target has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Getty on tty1...
-- Subject: Unit [email protected] has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit [email protected] has begun shutting down.
Jan 15 19:08:04 engserv systemd-logind[275]: Failed to abandon session scope: Transport endpoint is not connected
Jan 15 19:08:04 engserv systemd[364]: Stopping Default.
-- Subject: Unit UNIT has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has begun shutting down.
Jan 15 19:08:04 engserv systemd[364]: Stopped target Default.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Starting Generate shutdown-ramfs...
-- Subject: Unit mkinitcpio-generate-shutdown-ramfs.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit mkinitcpio-generate-shutdown-ramfs.service has begun starting up.
Jan 15 19:08:04 engserv systemd[364]: Stopping Basic System.
-- Subject: Unit UNIT has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has begun shutting down.
Jan 15 19:08:04 engserv systemd[364]: Stopped target Basic System.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has finished shutting down.
Jan 15 19:08:04 engserv systemd[364]: Stopping Timers.
-- Subject: Unit UNIT has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has begun shutting down.
Jan 15 19:08:04 engserv systemd[364]: Stopped target Timers.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has finished shutting down.
Jan 15 19:08:04 engserv systemd[364]: Stopping Paths.
-- Subject: Unit UNIT has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has begun shutting down.
Jan 15 19:08:04 engserv systemd[364]: Stopped target Paths.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has finished shutting down.
Jan 15 19:08:04 engserv systemd[364]: Stopping Sockets.
-- Subject: Unit UNIT has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Samba SMB/CIFS server...
-- Subject: Unit smbd.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit smbd.service has begun shutting down.
Jan 15 19:08:04 engserv systemd[364]: Stopped target Sockets.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has finished shutting down.
Jan 15 19:08:04 engserv systemd[364]: Starting Shutdown.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has begun starting up.
Jan 15 19:08:04 engserv systemd[364]: Reached target Shutdown.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has finished starting up.
-- The start-up result is done.
Jan 15 19:08:04 engserv systemd[364]: Starting Exit the Session...
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has begun starting up.
Jan 15 19:08:04 engserv systemd[364]: Received SIGRTMIN+24 from PID 8032 (kill).
Jan 15 19:08:04 engserv systemd[1]: Stopped User Manager for UID 1000.
-- Subject: Unit [email protected] has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit [email protected] has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping user-1000.slice.
-- Subject: Unit user-1000.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit user-1000.slice has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Removed slice user-1000.slice.
-- Subject: Unit user-1000.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit user-1000.slice has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Permit User Sessions...
-- Subject: Unit systemd-user-sessions.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-user-sessions.service has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped Permit User Sessions.
-- Subject: Unit systemd-user-sessions.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-user-sessions.service has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopping Remote File Systems.
-- Subject: Unit remote-fs.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit remote-fs.target has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Stopped target Remote File Systems.
-- Subject: Unit remote-fs.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit remote-fs.target has finished shutting down.
Jan 15 19:08:04 engserv systemd[1]: Unmounting /mnt/smb/share2...
-- Subject: Unit mnt-smb-share2.mount has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit mnt-smb-share2.mount has begun shutting down.
Jan 15 19:08:04 engserv systemd[1]: Unmounting /mnt/smb/share1...
-- Subject: Unit mnt-smb-share1.mount has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit mnt-smb-share1.mount has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: media-data.mount mount process exited, code=exited status=32
Jan 15 19:08:04 engserv nmbd[7459]: STATUS=daemon 'nmbd' finished starting up and ready to serve connectionsGot SIGTERM: going down...
Jan 15 19:08:04 engserv systemd[366]: pam_unix(systemd-user:session): session closed for user sth
Jan 15 19:08:05 engserv umount[8015]: umount: /media/data: target is busy
Jan 15 19:08:05 engserv umount[8015]: (In some cases useful info about processes that
Jan 15 19:08:05 engserv umount[8015]: use the device is found by lsof(8) or fuser(1).)
Jan 15 19:08:05 engserv systemd[1]: Unmounted /mnt/smb/share2.
-- Subject: Unit mnt-smb-share2.mount has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit mnt-smb-share2.mount has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Unmounted /mnt/smb/share1.
-- Subject: Unit mnt-smb-share1.mount has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit mnt-smb-share1.mount has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Network.
-- Subject: Unit network.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit network.target has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped target Network.
-- Subject: Unit network.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit network.target has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping dhcpcd on enp5s0...
-- Subject: Unit [email protected] has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit [email protected] has begun shutting down.
Jan 15 19:08:05 engserv dhcpcd[8049]: dhcpcd[8049]: sending signal TERM to pid 358
Jan 15 19:08:05 engserv dhcpcd[8049]: sending signal TERM to pid 358
Jan 15 19:08:05 engserv dhcpcd[8049]: waiting for pid 358 to exit
Jan 15 19:08:05 engserv dhcpcd[358]: received signal TERM from PID 8049, stopping
Jan 15 19:08:05 engserv dhcpcd[358]: enp5s0: removing interface
Jan 15 19:08:05 engserv dhcpcd[8049]: dhcpcd[8049]: waiting for pid 358 to exit
Jan 15 19:08:05 engserv mkinitcpio[8024]: ==> Starting build: none
Jan 15 19:08:05 engserv dhcpcd[358]: exited
Jan 15 19:08:05 engserv systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
Jan 15 19:08:05 engserv mkinitcpio[8024]: -> Running build hook: [sd-shutdown]
Jan 15 19:08:05 engserv systemd[1]: Stopped dhcpcd on enp5s0.
-- Subject: Unit [email protected] has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit [email protected] has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Unit [email protected] entered failed state.
Jan 15 19:08:05 engserv systemd[1]: [email protected] failed.
Jan 15 19:08:05 engserv systemd[1]: Stopping system-dhcpcd.slice.
-- Subject: Unit system-dhcpcd.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit system-dhcpcd.slice has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Removed slice system-dhcpcd.slice.
-- Subject: Unit system-dhcpcd.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit system-dhcpcd.slice has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Basic System.
-- Subject: Unit basic.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit basic.target has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped target Basic System.
-- Subject: Unit basic.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit basic.target has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Paths.
-- Subject: Unit paths.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit paths.target has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped target Paths.
-- Subject: Unit paths.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit paths.target has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
-- Subject: Unit systemd-ask-password-wall.path has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-ask-password-wall.path has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
-- Subject: Unit systemd-ask-password-wall.path has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-ask-password-wall.path has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
-- Subject: Unit systemd-ask-password-console.path has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-ask-password-console.path has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
-- Subject: Unit systemd-ask-password-console.path has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-ask-password-console.path has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Slices.
-- Subject: Unit slices.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit slices.target has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped target Slices.
-- Subject: Unit slices.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit slices.target has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping User and Session Slice.
-- Subject: Unit user.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit user.slice has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Removed slice User and Session Slice.
-- Subject: Unit user.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit user.slice has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Sockets.
-- Subject: Unit sockets.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sockets.target has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped target Sockets.
-- Subject: Unit sockets.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sockets.target has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping D-Bus System Message Bus Socket.
-- Subject: Unit dbus.socket has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dbus.socket has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Closed D-Bus System Message Bus Socket.
-- Subject: Unit dbus.socket has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dbus.socket has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Avahi mDNS/DNS-SD Stack Activation Socket.
-- Subject: Unit avahi-daemon.socket has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit avahi-daemon.socket has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
-- Subject: Unit avahi-daemon.socket has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit avahi-daemon.socket has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping System Initialization.
-- Subject: Unit sysinit.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sysinit.target has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped target System Initialization.
-- Subject: Unit sysinit.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sysinit.target has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Swap.
-- Subject: Unit swap.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit swap.target has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped target Swap.
-- Subject: Unit swap.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit swap.target has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Encrypted Volumes.
-- Subject: Unit cryptsetup.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit cryptsetup.target has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped target Encrypted Volumes.
-- Subject: Unit cryptsetup.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit cryptsetup.target has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
-- Subject: Unit systemd-update-utmp.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-update-utmp.service has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Load/Save Random Seed...
-- Subject: Unit systemd-random-seed.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-random-seed.service has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Setup Virtual Console...
-- Subject: Unit systemd-vconsole-setup.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-vconsole-setup.service has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped Setup Virtual Console.
-- Subject: Unit systemd-vconsole-setup.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-vconsole-setup.service has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Apply Kernel Variables...
-- Subject: Unit systemd-sysctl.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-sysctl.service has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped Apply Kernel Variables.
-- Subject: Unit systemd-sysctl.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-sysctl.service has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
-- Subject: Unit systemd-update-utmp.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-update-utmp.service has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Create Volatile Files and Directories...
-- Subject: Unit systemd-tmpfiles-setup.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-setup.service has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped Create Volatile Files and Directories.
-- Subject: Unit systemd-tmpfiles-setup.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-setup.service has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopping Local File Systems.
-- Subject: Unit local-fs.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit local-fs.target has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Stopped target Local File Systems.
-- Subject: Unit local-fs.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit local-fs.target has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: Unmounting /home...
-- Subject: Unit home.mount has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit home.mount has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Unmounting /run/user/1000...
-- Subject: Unit run-user-1000.mount has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit run-user-1000.mount has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Unmounting /boot...
-- Subject: Unit boot.mount has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit boot.mount has begun shutting down.
Jan 15 19:08:05 engserv systemd[1]: Unmounting Temporary Directory...
-- Subject: Unit tmp.mount has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit tmp.mount has begun shutting down.
Jan 15 19:08:05 engserv umount[8075]: umount: /home: target is busy
Jan 15 19:08:05 engserv umount[8075]: (In some cases useful info about processes that
Jan 15 19:08:05 engserv umount[8075]: use the device is found by lsof(8) or fuser(1).)
Jan 15 19:08:05 engserv systemd[1]: home.mount mount process exited, code=exited status=32
Jan 15 19:08:05 engserv systemd[1]: Failed unmounting /home.
-- Subject: Unit home.mount has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit home.mount has finished shutting down.
Jan 15 19:08:05 engserv systemd[1]: U -
Will not start on New Install. Opening goes straight to Crash reporter
Will not start on New Install. Clicking on icon does not open a window and goes straight to Crash reporter. I cannot access a window to try to open in safe mode (unless there is another method than outlined in the help article).
I run Windows XP and trying to install the latest 15.0.1 version. Before install, I did disable my Symantic virus protection. I have never used Firefox and would like to try it, but I'm having little success so far to even get started.
Please let me know if anyone has any other ideas or need more information from me.hello Singyt, the bug report associated to this kind of crash indicates that it might be a malware related issue.
your crash report also shows a file named "urixalog.dll", which doesn't turn up any search hits on google, which is also slightly suspicious. could you search for that file on your pc and upload it to a site like virustotal.com in order to analyze it.
please do a full scan of your system with the security software already in place and/or a different tool like the [http://www.malwarebytes.org/products/malwarebytes_free free version of malwarebytes].
[[Troubleshoot Firefox issues caused by malware]]
edit: the bug report also suggests that a monitoring program named spector pro/360/... which essentially acts like malware, might cause the issue. in case you have that installed please remove it. otherwise [https://support.mozilla.org/en-US/kb/Firefox%20crashes%20when%20you%20open%20it#w_backdoor-ulrbot-c here] would be a removal guide for urixalog.dll -
My Windows 7 Ultimate computer received an unauthorized Windows overnight update followed by error messages. Bless Microsoft. To compound the problem there were NO restore dates found and no recent backups. I lost about the last entire year of data including all my many downloads and recent documents, etc.
Like another user, I also had more than a year of Thunderbird emails in my inbox and many other folders. Important to me. Now TBird won't open...at all... and gives me an error message: "Your Thunderbird profile cannot be loaded. It may be missing or inaccessible." OK. So I uninstalled it and REINSTALLED IT, more than once, and still get this same error message after a supposedly successful installation. The error message and then TBird fails to open. Shouldn't it create a new profile with the new install?No. It's looking for, and finding, profiles.ini but can't find the profile in the location stored in profiles.ini.
Deleting (or moving or renaming) profiles.ini should indeed force it to generate a new profile.
Do these help?
http://kb.mozillazine.org/Recovering_a_profile_that_suddenly_disappeared
http://kb.mozillazine.org/Recovering_a_missing_profile -
adobe updater is crashing with adobe photoshop elements 6 and mac os version 10.9.4 (on a brand new install) . How to overcome this ?
Maybe I typed it wrong ...it is unchecked.
This is the message I receive:
Process: Adobe Updater
Path: /Applications/Utilities/Adobe Utilities.localized/*/Adobe Updater.app/Contents/MacOS/Adobe Updater
Identifier: "com.Adobe.ESD.AdobeUpdaterApplication"
Version: Adobe Updater 5.1.0.1082 (5.1.0.1082)
Code Type: X86 (Native)
Parent Process: launchd
Responsible: Adobe Updater
User ID: 501
Date/Time: 2014-11-21 12:39:47.691 -0600
OS Version: Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: 42CCAEE7-C520-BA70-4B27-711A184AB1A5
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
terminating with uncaught exception of type std::runtime_error: Unable to determine registration filepath!
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x93982952 __pthread_kill + 10
1 libsystem_pthread.dylib 0x96f15167 pthread_kill + 101
2 libsystem_c.dylib 0x940f029c abort + 155
3 libc++abi.dylib 0x99fe06c9 abort_message + 169
4 libc++abi.dylib 0x9a00147d default_terminate_handler() + 264
5 libc++abi.dylib 0x99ffec30 std::__terminate(void (*)()) + 14
6 libc++abi.dylib 0x99ffe64b __cxa_throw + 116
7 "com.Adobe.ESD.AdobeUpdaterApplication"0x0004e4a3 0x1000 + 316579
8 "com.Adobe.ESD.AdobeUpdaterApplication"0x00056f19 0x1000 + 352025
9 "com.Adobe.ESD.AdobeUpdaterApplication"0x00024499 0x1000 + 144537
10 "com.Adobe.ESD.AdobeUpdaterApplication"0x000139c0 0x1000 + 76224
11 "com.Adobe.ESD.AdobeUpdaterApplication"0x00002912 0x1000 + 6418
12 "com.Adobe.ESD.AdobeUpdaterApplication"0x0000282d 0x1000 + 6189
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x93983992 kevent64 + 10
1 libdispatch.dylib 0x96f1e899 dispatchmgr_invoke + 238
2 libdispatch.dylib 0x96f1e532 dispatchmgr_thread + 52
Thread 2:
0 libsystem_kernel.dylib 0x93983046 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x96f15dcf pthreadwqthread + 372
2 libsystem_pthread.dylib 0x96f19cce start_wqthread + 30
Thread 3:
0 libsystem_kernel.dylib 0x93983046 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x96f15dcf pthreadwqthread + 372
2 libsystem_pthread.dylib 0x96f19cce start_wqthread + 30
Thread 4:
0 libsystem_kernel.dylib 0x93983046 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x96f15dcf pthreadwqthread + 372
2 libsystem_pthread.dylib 0x96f19cce start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xa10e2c0c ecx: 0xbffff0dc edx: 0x93982952
edi: 0xa13a31a8 esi: 0x00000006 ebp: 0xbffff0f8 esp: 0xbffff0dc
ss: 0x00000023 efl: 0x00000206 eip: 0x93982952 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x99fe3e46
Logical CPU: 0
Error Code: 0x00080148
Trap Number: 132
Binary Images:
0x1000 - 0x24cff7 +"com.Adobe.ESD.AdobeUpdaterApplication" (Adobe Updater 5.1.0.1082 - 5.1.0.1082) <3D59867C-5698-4D46-AD1F-C357C48B75AA> /Applications/Utilities/Adobe Utilities.localized/*/Adobe Updater.app/Contents/MacOS/Adobe Updater
0x3ce000 - 0x3d9fff com.apple.CommerceCore (1.0 - 42) <D28DD970-4B69-3848-9BCC-3C67323B3D9C> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCor e.framework/Versions/A/CommerceCore
0x493f000 - 0x4964ff9 com.apple.framework.familycontrols (4.1 - 410) <A33A97EE-C735-38BA-9B49-5D78DAA3DEDA> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls
0x8fea6000 - 0x8fed8417 dyld (239.4) <0F2176BD-4239-3506-BA41-3B885269520E> /usr/lib/dyld
0x90008000 - 0x90023ff5 com.apple.openscripting (1.4 - 157) <5C161A52-8D2F-3D56-A988-05727BED7A59> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework /Versions/A/OpenScripting
0x90024000 - 0x90025fff liblangid.dylib (117) <F18F76C6-7E4B-34AD-AE81-C1C031BF2F7D> /usr/lib/liblangid.dylib
0x90026000 - 0x90109ff7 libcrypto.0.9.8.dylib (52) <D3AB1D26-30BA-36D3-956C-EC7D7185C396> /usr/lib/libcrypto.0.9.8.dylib
0x9010a000 - 0x90135ff7 libsystem_network.dylib (241.3) <71EBA489-386D-3608-ADE6-CB50EBD1AB1B> /usr/lib/system/libsystem_network.dylib
0x90136000 - 0x9052effb com.apple.CoreGraphics (1.600.0 - 599.35.4) <2B46D887-CAED-30F3-B009-1EBF0C71DC2E> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x9069c000 - 0x906a5fff com.apple.audio.SoundManager (4.1 - 4.1) <68B7CEB7-AF09-3E24-8548-6ABF065B5186> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/V ersions/A/CarbonSound
...and it goes on and on.
Joy (Awbrey) Schichtl
[email protected] -
My macbook started crashing on startup. The startup tone wavers. I got it going with the option start keystroke. Is this apt to be software or hardware? I ordered new system software to see if a new install will solve.
when you install the disc, do it with the machine powered off. Place the disc in the the slot, push it in while holding the power switch tp poer it up, while holding the "C" key down till the gear starts spinning. After the gear starts spinning you can release the C key and wait. This takes much longer than normal longer, then create a new account. Be ready to wait.
USE YOUR ORIGINAL INSTALL DISC! -
Each time I try to start firefox (FF), it crashes. I tried reinstalling new version couple of times, it is still crashing. I uninstalled:
J2SE Runtime Environment 5.0 Update 11
Jave 7 Update 9
Adobe Flash Player Plugin
Adobe Flash ActiveX
Adobe Shockware Player 11.6
After new install, FF is still crashing.
Crash ID: bp-86f02078-e5d6-4a3c-8b97-7df152130129
Crash ID: bp-6db32472-b5d3-4f25-af10-3e8f72130129The report for first Crash ID: bp-86f02078-e5d6-4a3c-8b97-7df152130129 is
https://crash-stats.mozilla.com/report/index/86f02078-e5d6-4a3c-8b97-7df152130129
Firefox 18.0.1 Crash Report [@ nsPrefBranch::GetIntPref(char const*, int*)
Related Bug:
[https://bugzilla.mozilla.org/show_bug.cgi?id=828184 828184] REOPENED --- startup crash in nsPrefBranch::GetIntPref with QIPCAP.dll (Websense Endpoint)
(The second Crash ID: [https://crash-stats.mozilla.com/report/index/6db32472-b5d3-4f25-af10-3e8f72130129 bp-6db32472-b5d3-4f25-af10-3e8f72130129] has the same signature and related bug)
QIPCAP.dll is a DLL that belongs to Websense Endpoint software https://www.websense.com/content/Home.aspx
'''Try Firefox Safe Mode''' to see how it works there. The Safe Mode is a troubleshooting mode, which disables most add-ons.''
* You can open Safe Mode by holding the '''Shift''' key when you use the Firefox desktop or Start menu shortcut and just use "'Start in Safe Mode"''
'''''If Firefox no longer crashes when you start in Firefox Safe Mode''''', your problem is probably caused by an extension related to Websense Endpoint software.
If Firefox still crashes in Safe Mode, you will need to contact Websense Endpoint support or else disable or uninstall that software and use another security product. -
New install of Elements 8 - Organizer crashes
New install of Elements 8 on Windows 7 64 bit machine. When I start the Organizer the program crashes and attempts to send a report to Adobe.
Since this is a brand new install and other programs are working nomally I am not sure where to go.
The log file of the Organizer is seen in blue below
Thanks for any helpThat's a new error I haven't seen before.
Try running the Organizer as administrator (which on Windows 7 is different than running in an account that's an administrator). Right-click the PSE icon on the desktop or the Start-menu item and select Run As Administrator. On some installations, PSE doesn't ensure that it has proper file permissions for all the folders and files it needs to write.
If that doesn't help, see these troubleshooting steps:
http://www.johnrellis.com/psedbtool/photoshop-elements-faq.htm#_Troubleshooting_Organizer_ crashes -
After Effects cs6 crashs on almost everything after new install
Hi,
I bought a new SSD to install Windows 7 64 bit and the software I'm used to working with on. After that install After Effect crashes as soon as I import a file. I've read other treads about the temp file paths but there all at %USERPROFILE%\AppData\Local\Tem I've haven't changed any settings.
Please if anyone can help!While I was updating the update manager said I need to close the ''Dynamic Link Media Server'' or something like that while the update manager was the only programm that was running, could something be going wrong there? Are there known problems with the dynamic link media server''?
What version of After Effects? Include the minor version number (e.g., After Effects CS5.5 with the 10.5.1 update).
After Effects cs6 with lastest update
Have you installed the recent updates? (If not, you should. They fix a lot of problems.)
Yes
What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".
Windows 7 64 bit, fresh install with servcice pack 1
What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".
Every type of footage I import
If you are getting error message(s), what is the full text of the error message(s)?
It just shuts dows
What were you doing when the problem occurred?
Importing footage
Has this ever worked before?
Yes, before the install
What other software are you running?
Nothing
Do you have any third-party effects or codecs installed?
No, I did install new catalyst drivers for vga
Tell us about your computer hardware. Include CPU type and number of processor cores, amount of RAM installed, GPU, number of disk drives, and how any external drives are connected.
Amd 4x 3000, 8gig, radeon 6450, one ssd
Do you have any third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU)?
No
Are you using OpenGL features in After Effects?
No
Does the problem only happen with your final output, RAM preview, or both?
I don´t get there
Are you using Render Multiple Frames Simultaneously multiprocessing?
No
What is the exact sequence of steps that you are taking?
New install, both Windows and Ae, new vga drivers. -
new macbook pro loaded with mavericks. installed CS3 including prompted Java update. try to open photoshop & empty splash screen pops up-can't go further. tried newer java update-same result. shut down 4 times-same. any suggestions?
Kappy wrote:
Has it occurred to you that CS3 isn't compatible with Mavericks? Try using CS9 or 10.
Sorry that's untrue. I have Photoshop CS3 running on 10.9.
CS9 or 10? Now you are just making stuff up.
Adobe claim CS3 will work, with a minor issue…
http://helpx.adobe.com/x-productkb/global/mac-os-mavericks-compatability.html
The Adobe updater fails to work for me.
I was prompted to install J6RE which came from Apple, check the Apple support downloads http://support.apple.com/downloads/#java%206
Sorry can't provide a direct link, it was just a dumb 'You need … please click install' dialog.
I think the 10.9 java updater is installing version 7.
Maybe you are looking for
-
Service Entry sheet to be set as Not accepted status
Hi After flagging the Transfer check box in the Settlement Tab in item details of shipment cost document(VI03), the Purchase order(ME23N) and Service entry sheet(ML81N) are automatically getting generated. PO and Service entry sheet numbers can be se
-
Problem not able to start my MacBook Pro 15 again
Recently i have updated my Mac OSX Leopard to Mac OSX Snow Leopard.Also i have changed the battery and i have format the hard drive completely when i install Mac OSX Snow Leopard. after the update i have start the mac two time and worked with office-
-
Need info regarding static file cache in weblogic
Hi, I want to cache the static files at weblogic side I am using Apache plugin provided by weblogic I have gone through the e-docs about FileCache ON which is needs to be set in httpd.conf I want to know is there any settings which is set at weblogic
-
Automatic refresh requisition status overview in MSS e-recruiting
Hi guys, We are implementing e-recruiting 6.0 and de MSS functionality to request a requisition with approvals. The manager can see his/her requests in the requisition status overview to follow-up. If we create a new requisition, the list is only upd
-
Is there a way to turn the GPS on my MacBook Pro off?
How do I turn the GPS on my MacBook Pro off? Everytime I log onto iCloud to find my iPhone it pops up too.