FCP HD Render problems... lots of random crashing... help!!

I'm using FCP to edit 8-bit uncompressed HD. Kona 3 card, Quad G5, 8.5Gbs RAM, Sonnet Tempo SATA card hooked up to two 8 bay raid towers totaling a little over 7TBs... RAID 0. OS X (10.4.7), FCP 5.1.1. The towers have 8 Seagate 500GB drives each... all run through port multiplier into four inputs on the Tempo SATA card (very fast, by the way).
I have changed computers, Kona 3 cards, memory, reloaded software, trashed prefs, rebuilt permissions, etc. Problem persist. I guess we've narrowed it down to the RAID, the Sonnet card or the software. I can't do anything about the software... and changing the storage would be VERY expensive. Any ideas or experience with this??
Is anyone successfully using a big SATA RAID w/ the Sonnet card?? I'm about to take a sledge hammer to this computer! Is anyone using an XRAID and NOT having problems with 8 or 10-bit uncompressed HD???
Please help!!
PowerMac Dual G5 Mac OS X (10.4.7)

Suggest you search for that specific camera model, might find some helpful suggestions from experienced users.
What format of "HD" are you shooting? There are about 50 different versions. If it's HDV, there is a huge volume of traffic to read through. A solution will depend largely on your machine's ability to decompress and build the i-frames on the fly.
bogiesan

Similar Messages

IPhone 6 plus randomly crashes help

hi I've had my iPhone 6 plus for a while now and recently it started crashing on its own it would randomly reboot on its own when I'm on a phone call it texting about anything it just would randomly crash
iI've also had issues with it freezing up on me multiple times any help?
I Always set up my iPhones as new so I didn't use a back up
tthe strange thing is that my if I'm on a phone call and it crashes it doesn't hang up the call as the phone reboots it will hold the call and I'm still on the phone even though it crashed and it's showing the apple logo as its rebooting
i dot know exactly what's going on but it happens randomly and its really annoying

Hi albertofromnewhall,
If your iPhone has been restarting unexpectedly I would suggest that you troubleshoot using the steps in this article -
iOS: Device unexpectedly restarts, displays Apple logo, or powers off
In particular, since you have the latest software update -
If you still see this issue after updating, contact Apple Support.
Thanks for using Apple Support Communities.
Best,
Brett L

Major FCP Glitching Render Problem - Any Ideas?

Hey folks, I'm running into massive render glitches with FCP. Here's what happens:
In a scene with a lot of fast cutting, and dupe frames, it all plays fine in realtime. However, once I render the footage, or make a self contained QuickTime, these areas lock up and get exported as freeze frames. These freeze frames are of the last frame of the previous clip before the cut. They stay on through the length of the next clip, and when FCP reaches the cut after that, it then plays fine again. It's very bizarre. It's almost like FCP can't keep up with accessing the media, and just skips the clip. I don't know why it would do that though, because it all plays as smooth as butter in realtime preview.
The only correlation that I've found is that there are dupe frames present in the areas where this is happening.
I've tried relocating my render drive to another disk drive... Deleting FCP preferences... Deleting render files... Pulling my Kona card... Nothing seems to fix the issue.
There's also another issue, which might be related. Whenever I try to apply certain filters, I get the following message, where EFFECT NAME is the name of a good number of effects:
"The effect 'EFFECT NAME' failed to render. Your hardware cannot render at the requested size and depth."
OR
"The effect 'EFFECT NAME' cannot be rendered in a sequence of this size with the current graphics card."
So, are these issues because I have the stock ATI Radeon 2600?
Here's my rig:
Sequence / Codec:
Apple ProRes 422 (normal) 1920x1080 23.98 psf
Mac:
FCP 6.0.3
OS X 10.5.2
2 x 3.2 GHz Quad-Core
8 GB 800 MHz Ram
ATI Radeon HD 2600
Kona 3 card with 5.1 drivers (latest)
Media Storage / Render Drive:
8TB Raid 5 ESATA storage
HighPoint ESATA controller card
ATI Radeon HD 2600:
Name: ATY,Lamna
Type: display
Driver Installed: Yes
Bus: PCI
Slot: Slot-1
Vendor ID: 0x1002
Device ID: 0x9588
Subsystem Vendor ID: 0x106b
Subsystem ID: 0x00a6
Revision ID: 0x0000
Link Width: x16
Any help or insight here would be extremely helpful!
Thank you in advance,
Blake

Tried that, no dice. The media is fine. It plays without a hitch when it doesn't need to be rendered, or if it's rendered with non problematic filters on it.
After fiddling with the freeze frame render glitch issue some more, it appears to be directly associated with "Basic Motion" changes.
I can stack tons of filters, and it doesn't happen. As soon as I move the shot around with "Basic Motion", it locks up the clip in the render, and creates a freeze frame.
Perhaps this is linked to the graphics card errors I am getting?

Render Problems on FCE...help!

I've been trying to edit this short film that I spontaneously decided to shoot with my digital camera (it's a canon powershot if that helps). I've edited one other project with footage from this camera and have had no problems. So far, I have sucessfully edited about 14 clips, however, now, whenever I try to render a new clip (and I have to because I have to resize all of them), the little box that says how much it has rendered and how long it will take, comes on for about .2 seconds and then goes away without rendering any of the footage. Sometimes, I it will go until it says "8%", and then goes away. What's weirder is that if I click cancel while it is rendering (which probably isn't good) it will have rendered some of the clip/a part of the red mark on the top goes away.
Yes, all the necessary tick marks are checked under the rendering settings and I tried to look up other settings under "easy setup", but I continue to have the same problem.

yes, because it's a digital camera, this probably the case. when i import my pictures and video from the camera to iPhoto, i can then put the video clips in a folder on my hard drive or desktop or wherever, and then just import them into FCE. i think the file type is AVI. for example, the clips all say MVI_00.74.AVI., so i'm assuming that's what it is. let me know if i'm wrong about that though.

Xorg randomly crashes

I have a problem where Xorg randomly crashes.
First the desktop becomes unresponsive, however I can move my cursor.
Using the mouse doesn't do anything, neither does my keyboard. Have tried going to a different tty, without any luck.
I usually grab my phone, login over ssh, and poweroff/reboot my machine to fix it.
The crashes occur kind of randomly, there isn't one program that when I start it will crash.
I have a Radeon HD 7870, using the open source drivers (don't really want to use the proprietary drivers, as I found it was slower on cli).
I have posted the Xorg.0.log on pastebin: http://pastebin.com/MRrYyKRr
I hope someone can help me with this.

I have the same problem as you describe and as described in the referenced thread. If it is the same bug, the problem may have been introduced in kernel v. 3.14.6 - see
https://bbs.archlinux.org/viewtopic.php?id=189081
Or it might not. Perhaps Xorg is the culprit, or maybe the open source Radeon driver.
Nobody knows when it will be fixed, if ever.

Adobe Media Encoder CS6 Random Crashing Mid-Render

Hello -
I've been dealing with this issue for enough months and across enough computers to finally seek out some advise here, hope it works out...
Basically I've got a 2 hour long film that I've been trying to export using Adobe Media Encoder CS6. It's never made it all the way through. I can usually skim through the generated quicktime file up to the point where the crash occurred. I've tried using that as a reference to check out my sequence in Premiere but there is never anything suspicious going on there. Most frustratingly the crash occurs randomly. Sometimes it will go through 10 minutes of the film; sometimes an hour. Regardless I get a crash with a report that has no specific information.
Footage:
r3d - Various resolutions, all being cut in a 2048x1152 sequence.
Quicktime mov - ProRes4444 for the most part.
Machine(s):
I had been attempting to render this for the past few months with a Macbook Pro running OSX 10.8.4 w/ 16GB RAM, 2.7 GHz Intel i7, NVIDIA GeForce GT 650M 1024MB - never made it through a render longer than 50 minutes of the 2 hours.
We recently got one of the new 2013 Mac Pro systems running OSX 10.9 w/ 16GB RAM, 3.5 GHz 6-Core Intel Xeon E5, AMD FirePro D500 3072 MB
The hope was that this new powerful machine would overcome the issues we were running into with these renders. Since I'm posting this now you can probably figure out that it didn't really work out that way...
Software:
AME- 6.0.2.81
Premiere - 6.0
I know there are updates to be used here, but whenever I update Premiere from just 6.0, the project itself becomes a buggy mess, crashing constantly. I also run Creative Cloud and have tried to just jump over to Premiere CC hoping all my problems would vanish, but instead, I again get a buggy project that constantly crashes. The only version of Premiere that seems to work with this project is 6.0, so general updates have not been useful (and instead damaging, I've wasted several days trying everything I possibly can to make the project work in the updates).
Any help appreciated. Thanks.

Thanks for the reply MMeguro.
Last night I was able to get my first full render through by doing a combination of things (so I'm not sure what did the trick in the end).
To answer some questions first, never attempted to do the FULL render directly out of Premiere, always switched over to AME for that, so that potentially could work too. Smaller renders have worked directly out of Premiere Pro, but they've also worked out of AME.
The initial render attempts that had been failing for the last few months were on the MBP which did not support GPU accleration due to an incompatible graphics card. I assumed the issue must be tied to something else because of this and was using it on the renders with the new 2013 Mac Pro. Using the workflow of Pr6.0, AME 6.0 and GPU rendering turned ON, I was failing to render to both Quicktime h264 and ProRes 422.
What worked for last night's render:
1. Convert Pr6.0 project to PrCC project (when I've done actual editing in CC after converting this project it tends to crash, but I figured just generating the project itself without doing any editing in it might satisfy what I was attempting to do).
2. Open AME CC and import PrCC Sequence. Used custom ProRes 422 setting.
3. Turned OFF GPU acceleration.
So as long as I the PrCC project I create stays stable long enough to save it (without crashing, which has been a problem with that Pr6.0 to PrCC conversion) then it seems like this will work. Kind of an annoying couple extra steps but I'm just out of my mind glad that I can actually render this thing finally. We're still in the rough stages so being able to turn around a review version within a day is very important.
Wish I could do more tests to figure out exactly which combination actually made this work for the benefit of others, but can't afford to do multiple 10 hour+ renders with random crash times.
Anyway, thanks again for the reply MMeguro much appreciated.

Problems with Windows and Random Crashes

For the past two days I have been having tons of problems, since I finally got around to running the security update (2006-008). I've been having loads of random crashes, most commonly from Safari, Finder and iTunes. Safari crashes usually when I close a window or interact with certain flash things. It also fails to draw the window when I close the second-to-last tab (leaving one tab), giving me a big white square that I have to close. Otherwise, random window elements (such as bookmarks bar, address bar, etc.) will disappear at random, or will be horribly mis-sized.
Finder just quits whenever it wants, I have yet to find a common thread between crashes.
iTunes crashes usually when I play a video, but also sometimes when switching from the store to a playlist, or to the library. It also suffers occasional redraw problems similar to Safari, though not as bad. Garage Band does too.
Here's the output from the last iTunes crash, if it provides any clues:
EXCBADACCESS (0x0001)
KERNINVALIDADDRESS (0x0001) at 0xffffffff
Thread 0 Crashed:
0 GetPatternIdentifier + 211
1 SetPortPat + 103
2 BackPixPat + 42
3 DataEngine::ApplyBrush(TTheme*, short, unsigned char) + 76
4 SetThemeBackground + 836
5 SetThemeWindowBackground + 292
6 NewFeaturesDialog + 202
7 CreateDialog(Rect const*, unsigned char const*, unsigned char, short, OpaqueWindowPtr*, unsigned char, long, char**, ColorTable**, char**, char**, unsigned long, unsigned char, AutoPositionInfo) + 175
8 GetNewDialog + 173
9 0x1000 + 1686314
All of my crashes have been EXCBADACCESS (0x0001) ones.
Please help, as this is a nightmare to deal with.

That error usually comes up as a result of faulty RAM. Did you buy any chance upgrade the RAM in your iMac? If so, verify that the chip is seated properly and that it is supported for your iMac.

Thumbnail view crashing FCP -- Kona3 the problem?

For larger projects, running bins in thumbnail view crashes FCP.
Most of the time, I'm editing 6 to 8 min. stories for a news magazine format show. We shoot on Sony XDCAM, so usually 2 or 3 disks per project (roughly 44 mins of HD viddy per disk, with anywhere from 20 to 120 individual clips on the disk).
However, for our documentaries (either 26 mins or 56mins) we shoot between 30 to 45 disks full of content. When importing the disks into FCP7, we use a bin per disc, translating into an average of 80 clips per bin. Whenever a project is this big, I can only open 3 or so bins in thumbnail view. After that, the system crashes. Even if I only keep one bin open at a time, by that fourth bin, the system crashes.
We are using a KONA3 card configuration.
Anyone else seen this?

PROBLEM IDENTIFIED (NOT SOLVED):
I've had this problem with thumbnail images crashing FCP after opening bins for over a year now and when going back using footage from old projects it happens more frequently. I can open 2-4 bins before it will crash FCP completely.
TROUBLESHOOTING IN THE PAST:
- Dumped Prefs
- Re-installed FCP
- Formatted & Re-installed EVERYTHING (OSX included)
- Increased thumbnail cache size
- Created new projects & bins, etc.
CONCLUSION:
None of the above troubleshooting strategies worked. Increasing the thumbnail cache size may appear to work a little but problem persists with little improvement.
HOW I IDENTIFIED THE PROBLEM:
Only recently have I been working with other formats aside from XDCAM. I've recently incorporated more ProRes files into my most recent project of T2i footage from the Canon DSLR camera. If I open a bin and display thumbnails of the ProRes video clips everything works without a problem. Loading thumbnail bins with the raw .mp4 files also works fine. Only loading XDCAM files will cause FCP to crash. The problem has nothing to do with the Kona card. If you read the posts carefully here and elsewhere you will see the common denominator is the XDCAM encoded video files being displayed as thumbnail icons.
I am using XDCAM EX files at 1080p 30fps. To further isolate this problem as something having to do with the XDCAM files, another user posted on another thread:
*"I am having similar issues with two separate projects. The only commonality between them is XDCam.*
*To possibly isolate it I reinstalled FCP on one system, and installed latest Blackmagic driver on the the same. Both systems are up to date visa vi OS, FCP, and QT.*
*Both still crash with the same regularity as described here."*
Apple, this problem has persisted for more than two years and is a major problem. Just search the forums including this one. Any further upgrades of Final Cut Studio or OS X are worthless until this problem is fixed. A brand new body and interior won't fix a car with a broken engine. Please help!! Please solve this issue with the XDCAM footage in FCP!
If anyone has any solutions or work arounds please notify me. I need it!
[email protected]
/\/\ichael
Message was edited by: MichaelRev1412
Message was edited by: MichaelRev1412

I'm using an older mac (2008 iMac). Things were fetting slow and I used a program called DupZapper to get rid of a lot of duplicate files. It worked and my computer is running better. The only problem is now InDesign crashed at startup. I have the ori

I'm using an older mac (2008 iMac). Things were getting slow and I used a program called DupZapper to get rid of a lot of duplicate files. It worked and my computer is running better. The only problem is now InDesign crashes at startup. I have the original disks and serial number (CS3) The error message is "required resources are missing". Same message if I try to uninstall. Any clues as to how to re-install?

reset your preferences and retry launching id: InDesign Help | Setting preferences
if that fails, uninstall (properly with the uninstaller), clean and reinstall per Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6

Random crash and gyroscope problems (Iphone iOS 6.1)

Since the last iOS update (6.1). I have experienced a few problems with my Iphone 5.
First of all the day that i updated the iOS, i started getting random crashes.The screen dimmed and 2 or 3 yellow vertical lines appeared, and short after the Iphone restarted itself. The crash was happening mostly when opening the camera or any app that used the camera, but it will also restart by just browsing through the home screen (less likely). Then i noticed that some apps that use the gyroscope where locking up (like panorama 360), and a message telling me to restart the iphone because the gyro was locked up (i checked pressing home twice and the gyro wasn't locked). After the restart i worked for about 15 minutes, and the gyro would stuck up again (and the crashes were getting worse). I decided to do a factory recovery, and it solve most of the problems, but i still get 1 or 2 crashes everyday (maybe more, because i dont know if the cellphone restarts when it is in my pocket) (and it now doesnt restart by using the camera), and the gyroscope sometimes works fine, and very few times it stucks up, so i close the app that uses it, lock the gyro, give the phone a few shakes, put the gyro back on and it works again.
I'm trying to simulate the moments that the phone crashes or when the gyro stucks up, but i can't, it is just very random.
PD: The phone worked perfectly with iOS 6.0.1, could be a software problem? hardware problem?
PD2: i have used linpack to stress the phone but it doesnt crash or anything.

The video is here
https://www.youtube.com/watch?v=ZNh5b-0F9o8
The last two day i haven't experienced crashes but sometimes the gyro stucks.
PD:sorry if the video is in spanish, but you can see the problems.

[VIA] Random crashes problem

Ok, ive had this problem since i bought my PC(2 years ago).
Local stores 1st told me was my HDD, so i changed it
Then they told me was my Videocard, so i changed it
After told me it was my motherboard, so i changed it
again i got told was my video card, i bougt a better one
i also got told to update my BIOS, my friend is a PC expert, so he flashed it everything went fine;
Then i went here or on AMD forum and i got told my PSU wasnt strong enuf i bought a very good antec psu for 150$
between each of thoses steps the issues seemed to be fixes but no it all starts again...
When i bought my new psu, i reformated and it went fine for a couple of months...
its now back...random crashes...no blue screen, it only restarts or becomes not responding.
im very pissed and i want answeres cuz i paid alot for my pc...
here are my specs
mobo = KT6 Delta, MS-6590 (v2.X) ATX latest bios update
cpu = AMD Athlon XP 2800+
videocard = ATI radeon 9600XT 256mb
ram = 2x512mb DDR 400 MHZ
dvd = HL-DT-ST DVDRAM GSA-4040B
cd = HL-DT-ST CD-RW GCE-8523B
2HDD = 200gb and 160gb
PSU = Antec Smartpower 350

heres my PSU model
http://www.antec.com/specs/SP350_spe.html
also i posted on AMD forum and some ppl suggested me some changes in my bios but its still crash...
heres my new report
CPU(s)
Number of CPUs 1
Name AMD Athlon XP
Code Name Barton
Specification AMD Athlon(tm) XP 2800+
Family / Model / Stepping 6 A 0
Extended Family / Model 7 A
Package Socket A
Technology 0.13 µ
Supported Instructions Sets MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE
CPU Clock Speed 2085.0 MHz
Clock multiplier x 12.5
Front Side Bus Frequency 166.8 MHz
Bus Speed 333.6 MHz
L1 Data Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache 512 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed 2085.0 MHz (Full)
L2 Location On Chip
L2 Data Prefetch Logic yes
L2 Bus Width 64 bits
Mainboard and chipset
Motherboard manufacturer MSI
Motherboard model MS-7021, 1.0
BIOS vendor American Megatrends Inc.
BIOS revision Version 07.00T
BIOS release date 04/02/01
Chipset VIA KT600 rev. 80
Southbridge VIA VT8237 rev. 00
Sensor chip Winbond W83697HF
Graphic Interface AGP
AGP Status enabled, rev. 3.5
AGP Data Transfer Rate 8x
AGP Max Rate 8x
AGP Side Band Addressing supported, enabled
AGP Aperture Size 256 MBytes
Memory
DRAM Type DDR-SDRAM
DRAM Size 1024 MBytes
DRAM Frequency 166.8 MHz
FSB:DRAM 1:1
DRAM Interleave 4-way
CAS# Latency 2.5 clocks
RAS# to CAS# 3 clocks
RAS# Precharge 3 clocks
Cycle Time (TRAS) 8 clocks
# of memory modules 2
Module 0 DDR-SDRAM PC3200 - 512 MBytes
Module 1 DDR-SDRAM PC3200 - 512 MBytes
Software
Windows version Microsoft Windows XP Professional Service Pack 2 (Build 2600)
DirectX version 9.0c

Some random crashing problems in AE CS3...

So I've only had CS3 for about a month now (had 6.5 forever) and I'm having some stability problems. Using vista 64 but had the same problems in 32 bit vista (and windows 7 which I tried for about a week).
First it was crashing because of divx, I uninstalled divx.
Then it seemed that Cineform Neoscene was crashing it, they released an update and I reinstalled Neo scene with the update and that stopped crashing it. Now I get somewhat random crashes that just say App crash and I get a message pop up that says
"Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:\Program Files (x...
R6025
-pure vital function call"
What is this and how do I stop it from happening? It seemes to happen in Encore and Premiere aswell.
I am running as administrator...
Thanks.

Most of the footage is cineform files, converted using the latest version of neo scene. But its happened before I've even opened a project or imported any kind of files. Audio is PCM. Sometimes the error will come up and if I hit x instead of "close the program" it stays running just fine, other times it will close.
Adobe updater updated everything by itself, know it updated all the core programs, etc. (using Production Premium)
Every available vista update is installed including service pack 2. Latest nVidia drivers, etc. I ran spybot and antivirus software today.
All the OS were on the same system but the HDD was completely formatted inbetween installs. Yes W7 RC was used.
Core 2 Duo T9300
4GB RAM
nVidia 8600M
1 internal 320GB HDD
1 external esata 1TB HDD
Blu ray read + write drive
I have a feeling it could be something to do with Cineform but what and why?
EDIT -
It just happened when I tried to open Encore and crashed before the program even started with this in the details:
Problem Event Name: APPCRASH
Application Name: Adobe Encore.exe
Application Version: 3.0.1.8
Application Timestamp: 46cf7628
Fault Module Name: libguide40.dll
Fault Module Version: 4.0.2007.602
Fault Module Timestamp: 4661a089
Exception Code: c0000005
Exception Offset: 000133f0
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Random crashes in down_read_trylock, since 3.18.6 kernelver =3.19.2

Hello all,
On 05 Apr 2015, I did a full upgrade (pacman -Syu), including a kernel update:
[2015-04-05 19:32] [ALPM] upgraded linux (3.18.6-1 -> 3.19.2-1)
and since then I have been getting random crashes. I suspect an obscure kernel bug crept in somewhere after 3.18.6 (that version was working fine) and before (or in) 3.19.2. I have been doing full upgrades every week or so (and also upgrading Xen from AUR), in the hope that the bug would go away, but it hasn't.
I run a few Xen virtual machines, so there's obviously a lot of virtual memory coming and going, but I have run memtest86 successfully (one complete runthrough), so I do not suspect the memory hardware.
Looking in the journal for log messages, I see CPU register and stack trace dumps (see end note 1). I notice (end notes 2 and 3) that the function down_read_trylock (from linux/kernel/locking/rwsem.c) is in nearly all the crashes, and it's being called from the page_lock_anon_vma_read (from linux/mm/rmap.c) function (end note 4).
The file kernel/locking/rwsem.c has not changed between 3.18.6 and 3.19.2 (using the vanilla kernel sources from kernel.org), but mm/rmap.c has changed quite a bit. In particular, references to
mapping->i_mmap_mutex
have been replaced with
mapping->i_mmap_rwsem
For full diff, see end note 6.
In addition, taint info (see end note 5) shows the flags G=kernel, O=oot_module, and sometimes D=died (info from linux/kernel/panic.c and linux/include/linux/kernel.h). I expect to see G and D, but not O. I'm not sure if this indicates there's been a problem while loading/unloading a module. The current value of /proc/sys/kernel/tainted (on my currently running system) is 4096, which is 1<<12, which is the O=oot_module flag, so perhaps it can be ignored since it seems it's always present.
I'm a little out of my depth by now, having not done any kernel bug tracing or debuging before, so I guess my questions are:
Has anyone else been having the same or similar probems?
Might someone have some suggestions for how I should investigate further?
(Postscript: I've read How to Ask Questions the Smart Way, but if I've forgotten to do something obvious or post some obvious info, then apologies.)
End notes:
Here is a complete crash dump log. In this case, snmpd died, though the process that dies is not consistent (see end note 5)
May 29 11:23:46 hoom kernel: general protection fault: 0000 [#1] PREEMPT SMP
May 29 11:23:46 hoom kernel: Modules linked in: uas usb_storage dm_crypt loop dm_mod tun xt_physdev br_netfilter fuse bridge stp llc xt_nat iptable_nat nf_nat_ipv4 nf_nat nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack it87 iptable_filter hwmon_vid ip_tables x_tables amdkfd amd_iommu_v2 crct10dif_pclmul crc32_pclmul crc32c_intel radeon ghash_clmulni_intel snd_hda_codec_via snd_hda_codec_hdmi snd_hda_codec_generic joydev aesni_intel ttm evdev snd_hda_intel aes_x86_64 mousedev lrw snd_hda_controller gf128mul glue_helper ablk_helper drm_kms_helper mac_hid snd_hda_codec psmouse cryptd r8168(O) snd_hwdep snd_pcm edac_core sp5100_tco edac_mce_amd drm snd_timer pcspkr serio_raw i2c_piix4 k10temp fam15h_power snd i2c_algo_bit tpm_infineon r8169 i2c_core mii soundcore
May 29 11:23:46 hoom kernel: tpm_tis tpm shpchp button sch_fq_codel xen_acpi_processor processor xen_pciback xen_netback xen_blkback nfsd xen_gntalloc xen_gntdev xen_evtchn auth_rpcgss nfs oid_registry nfs_acl lockd fscache grace xenfs sunrpc xen_privcmd ext4 crc16 mbcache jbd2 sd_mod ata_generic pata_acpi hid_logitech_hidpp hid_logitech_dj usbhid hid atkbd libps2 pata_atiixp ahci libahci xhci_pci ohci_pci libata ehci_pci ohci_hcd ehci_hcd xhci_hcd usbcore scsi_mod usb_common i8042 serio
May 29 11:23:46 hoom kernel: CPU: 6 PID: 578 Comm: snmpd Tainted: G O 4.0.4-2-ARCH #1
May 29 11:23:46 hoom kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./970A-UD3P, BIOS F1 08/06/2013
May 29 11:23:46 hoom kernel: task: ffff880816a32880 ti: ffff88080cbfc000 task.ti: ffff88080cbfc000
May 29 11:23:46 hoom kernel: RIP: e030:[<ffffffff810bdc59>] [<ffffffff810bdc59>] down_read_trylock+0x9/0x30
May 29 11:23:46 hoom kernel: RSP: e02b:ffff88080cbff648 EFLAGS: 00010206
May 29 11:23:46 hoom kernel: RAX: 0000000000000000 RBX: ffff88010087a910 RCX: 0000000016191b1c
May 29 11:23:46 hoom kernel: RDX: ffffffff8119ac30 RSI: ffff88080cbff6e8 RDI: 151515151515151d
May 29 11:23:46 hoom kernel: RBP: ffff88080cbff648 R08: 0000000000017938 R09: 0000000000000002
May 29 11:23:46 hoom kernel: R10: ffff8807df6cc000 R11: 0000000000000003 R12: ffff88010087a911
May 29 11:23:46 hoom kernel: R13: ffffea0004322500 R14: 151515151515151d R15: ffffea0004322500
May 29 11:23:46 hoom kernel: FS: 00007f771616c700(0000) GS:ffff880820980000(0000) knlGS:0000000000000000
May 29 11:23:46 hoom kernel: CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
May 29 11:23:46 hoom kernel: CR2: 00007f77161a2000 CR3: 000000080c969000 CR4: 0000000000040660
May 29 11:23:46 hoom kernel: Stack:
May 29 11:23:46 hoom kernel: ffff88080cbff678 ffffffff8119ac8e ffff88080cbff6e8 ffffea0004322500
May 29 11:23:46 hoom kernel: ffffea000b8e7480 ffff88010087a911 ffff88080cbff6d8 ffffffff8119aef3
May 29 11:23:46 hoom kernel: 0000000000000000 ffffea0004322580 ffffea000b8cb580 0000000000000000
May 29 11:23:46 hoom kernel: Call Trace:
May 29 11:23:46 hoom kernel: [<ffffffff8119ac8e>] page_lock_anon_vma_read+0x5e/0x130
May 29 11:23:46 hoom kernel: [<ffffffff8119aef3>] rmap_walk+0x193/0x330
May 29 11:23:46 hoom kernel: [<ffffffff8119b2dc>] try_to_unmap+0x6c/0xb0
May 29 11:23:46 hoom kernel: [<ffffffff81199f10>] ? page_remove_rmap+0x120/0x120
May 29 11:23:46 hoom kernel: [<ffffffff81199360>] ? invalid_migration_vma+0x30/0x30
May 29 11:23:46 hoom kernel: [<ffffffff8119ac30>] ? page_get_anon_vma+0xc0/0xc0
May 29 11:23:46 hoom kernel: [<ffffffff81199330>] ? invalid_mkclean_vma+0x20/0x20
May 29 11:23:46 hoom kernel: [<ffffffff811c1237>] migrate_pages+0x4a7/0x910
May 29 11:23:46 hoom kernel: [<ffffffff811842d0>] ? pageblock_pfn_to_page+0xe0/0xe0
May 29 11:23:46 hoom kernel: [<ffffffff81185ca0>] ? isolate_freepages_block+0x3c0/0x3c0
May 29 11:23:46 hoom kernel: [<ffffffff8118706e>] compact_zone+0x4be/0x870
May 29 11:23:46 hoom kernel: [<ffffffff813859f2>] ? xen_send_IPI_one+0x32/0x70
May 29 11:23:46 hoom kernel: [<ffffffff8118748a>] compact_zone_order+0x6a/0x90
May 29 11:23:46 hoom kernel: [<ffffffff81187752>] try_to_compact_pages+0x102/0x280
May 29 11:23:46 hoom kernel: [<ffffffff81167793>] __alloc_pages_direct_compact+0x43/0x100
May 29 11:23:46 hoom kernel: [<ffffffff81167dc0>] __alloc_pages_nodemask+0x570/0x9f0
May 29 11:23:46 hoom kernel: [<ffffffff811682ba>] alloc_kmem_pages_node+0x7a/0x150
May 29 11:23:46 hoom kernel: [<ffffffff811b640c>] kmalloc_large_node+0x2c/0x60
May 29 11:23:46 hoom kernel: [<ffffffff811bd8c5>] __kmalloc_node_track_caller+0x275/0x320
May 29 11:23:46 hoom kernel: [<ffffffff814a72a6>] ? __netlink_dump_start+0x176/0x1b0
May 29 11:23:46 hoom kernel: [<ffffffff81464bd7>] ? __alloc_skb+0x87/0x210
May 29 11:23:46 hoom kernel: [<ffffffff81464af1>] __kmalloc_reserve.isra.5+0x31/0x90
May 29 11:23:46 hoom kernel: [<ffffffff81527fb0>] ? inet6_dump_ifmcaddr+0x20/0x20
May 29 11:23:46 hoom kernel: [<ffffffff81464bab>] ? __alloc_skb+0x5b/0x210
May 29 11:23:46 hoom kernel: [<ffffffff81464bd7>] __alloc_skb+0x87/0x210
May 29 11:23:46 hoom kernel: [<ffffffff814a4ed2>] netlink_alloc_skb+0x62/0x1e0
May 29 11:23:46 hoom kernel: [<ffffffff814a6a03>] netlink_dump+0xc3/0x2d0
May 29 11:23:46 hoom kernel: [<ffffffff814a6e7d>] netlink_recvmsg+0x26d/0x340
May 29 11:23:46 hoom kernel: [<ffffffff81459da2>] sock_recvmsg_nosec+0x52/0x80
May 29 11:23:46 hoom kernel: [<ffffffff8145c1dd>] SyS_recvfrom+0x11d/0x1a0
May 29 11:23:46 hoom kernel: [<ffffffff814587e6>] ? sock_alloc_file+0xa6/0x140
May 29 11:23:46 hoom kernel: [<ffffffff811f6bbd>] ? __fd_install+0x4d/0x70
May 29 11:23:46 hoom kernel: [<ffffffff811f6c05>] ? fd_install+0x25/0x30
May 29 11:23:46 hoom kernel: [<ffffffff8145b58f>] ? SyS_socket+0x9f/0xf0
May 29 11:23:46 hoom kernel: [<ffffffff8157a449>] system_call_fastpath+0x12/0x17
May 29 11:23:46 hoom kernel: Code: 6e bf 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 b7 a8 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 29 11:23:46 hoom kernel: RIP [<ffffffff810bdc59>] down_read_trylock+0x9/0x30
May 29 11:23:46 hoom kernel: RSP <ffff88080cbff648>
May 29 11:23:46 hoom kernel: ---[ end trace 32e90ce275ac679e ]---
May 29 11:23:46 hoom systemd[1]: snmpd.service: main process exited, code=killed, status=11/SEGV
May 29 11:23:46 hoom systemd[1]: Unit snmpd.service entered failed state.
May 29 11:23:46 hoom systemd[1]: snmpd.service failed.
Looking for IP in the journal:
journalctl >/tmp/journal ; grep ' kernel: IP: ' /tmp/journal | less
Output:
Apr 06 11:00:02 hoom kernel: IP: [<ffffffff810bafc9>] down_read_trylock+0x9/0x30
Apr 06 11:00:03 hoom kernel: IP: [<ffffffff810bafc9>] down_read_trylock+0x9/0x30
Apr 06 11:00:04 hoom kernel: IP: [<ffffffff810bafc9>] down_read_trylock+0x9/0x30
Apr 16 08:32:26 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 15:44:20 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:52 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:18:18 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:18:18 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:18:19 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:20:00 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:20:00 hoom kernel: IP: [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
May 11 09:38:10 hoom kernel: IP: [<ffffffffa012805d>] gntdev_vma_find_special_page+0x1d/0x30 [xen_gntdev]
May 13 17:46:39 hoom kernel: IP: [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:45:00 hoom kernel: IP: [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:45:27 hoom kernel: IP: [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:49:39 hoom kernel: IP: [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:50:00 hoom kernel: IP: [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:50:00 hoom kernel: IP: [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:50:00 hoom kernel: IP: [<ffffffff81093840>] kthread_data+0x10/0x20
May 14 08:50:00 hoom kernel: IP: [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:50:00 hoom kernel: IP: [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
Looking for RIP in the journal:
journalctl >/tmp/journal ; grep ' kernel: RIP: ' /tmp/journal | less
Output:
Apr 06 11:00:03 hoom kernel: RIP: e030:[<ffffffff810bafc9>] [<ffffffff810bafc9>] down_read_trylock+0x9/0x30
Apr 06 11:00:03 hoom kernel: RIP: e030:[<ffffffff810bafc9>] [<ffffffff810bafc9>] down_read_trylock+0x9/0x30
Apr 06 11:00:04 hoom kernel: RIP: e030:[<ffffffff810bafc9>] [<ffffffff810bafc9>] down_read_trylock+0x9/0x30
Apr 06 11:00:04 hoom kernel: RIP: e030:[<ffffffff810bafc9>] [<ffffffff810bafc9>] down_read_trylock+0x9/0x30
Apr 16 08:32:26 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 13:49:42 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 13:58:42 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 14:00:00 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 14:02:29 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 14:02:29 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 14:15:00 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 14:15:48 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 14:26:34 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 14:44:00 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 14:50:03 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 15:08:11 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 15:31:48 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 15:44:20 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 16:04:01 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 16:04:01 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 16 16:37:55 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:50 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:17:52 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:18:18 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:18:18 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:18:19 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:20:00 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
Apr 26 09:20:00 hoom kernel: RIP: e030:[<ffffffff810bb0a9>] [<ffffffff810bb0a9>] down_read_trylock+0x9/0x30
May 11 09:38:10 hoom kernel: RIP: e030:[<ffffffffa012805d>] [<ffffffffa012805d>] gntdev_vma_find_special_page+0x1d/0x30 [xen_gntdev]
May 13 17:46:39 hoom kernel: RIP: e030:[<ffffffff810bdb09>] [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:45:00 hoom kernel: RIP: e030:[<ffffffff810bdb09>] [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:45:27 hoom kernel: RIP: e030:[<ffffffff810bdb09>] [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:49:39 hoom kernel: RIP: e030:[<ffffffff810bdb09>] [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:50:00 hoom kernel: RIP: e030:[<ffffffff810bdb09>] [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:50:00 hoom kernel: RIP: e030:[<ffffffff810bdb09>] [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:50:00 hoom kernel: RIP: e030:[<ffffffff81093840>] [<ffffffff81093840>] kthread_data+0x10/0x20
May 14 08:50:00 hoom kernel: RIP: e030:[<ffffffff810bdb09>] [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 14 08:50:00 hoom kernel: RIP: e030:[<ffffffff810bdb09>] [<ffffffff810bdb09>] down_read_trylock+0x9/0x30
May 21 21:05:28 hoom kernel: RIP: e030:[<ffffffff810bdc59>] [<ffffffff810bdc59>] down_read_trylock+0x9/0x30
May 22 09:45:38 hoom kernel: RIP: e030:[<ffffffff810bdc59>] [<ffffffff810bdc59>] down_read_trylock+0x9/0x30
May 22 09:57:35 hoom kernel: RIP: e030:[<ffffffff810bdc59>] [<ffffffff810bdc59>] down_read_trylock+0x9/0x30
May 22 09:57:55 hoom kernel: RIP: e030:[<ffffffff810bdc59>] [<ffffffff810bdc59>] down_read_trylock+0x9/0x30
May 29 11:23:46 hoom kernel: RIP: e030:[<ffffffff810bdc59>] [<ffffffff810bdc59>] down_read_trylock+0x9/0x30
Looking for the function at the top of the call trace stack:
journalctl >/tmp/journal ; grep -A1 'Call Trace' /tmp/journal | grep 0x | less
Output:
Apr 06 11:00:03 hoom kernel: [<ffffffff81196a3e>] page_lock_anon_vma_read+0x5e/0x130
Apr 06 11:00:03 hoom kernel: [<ffffffff81196a3e>] page_lock_anon_vma_read+0x5e/0x130
Apr 06 11:00:04 hoom kernel: [<ffffffff81196a3e>] page_lock_anon_vma_read+0x5e/0x130
Apr 06 11:00:04 hoom kernel: [<ffffffff81196a3e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 08:32:26 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 13:49:42 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 13:58:42 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 14:00:00 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 14:02:29 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 14:15:00 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 14:15:48 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 14:26:34 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 14:44:00 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 14:50:03 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 15:08:11 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 15:31:48 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 15:44:20 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 16:04:01 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 16:04:01 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 16 16:37:55 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:17:50 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:17:50 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:17:50 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:17:50 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:17:50 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:17:52 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:18:18 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:18:18 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:18:19 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:20:00 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
Apr 26 09:20:00 hoom kernel: [<ffffffff81196b9e>] page_lock_anon_vma_read+0x5e/0x130
May 11 09:38:10 hoom kernel: [<ffffffff8118ab4a>] ? vm_normal_page+0x7a/0xb0
May 11 09:38:10 hoom kernel: [<ffffffff8156de97>] dump_stack+0x4c/0x6e
May 13 17:46:39 hoom kernel: [<ffffffff811997ae>] page_lock_anon_vma_read+0x5e/0x130
May 14 08:45:00 hoom kernel: [<ffffffff811997ae>] page_lock_anon_vma_read+0x5e/0x130
May 14 08:45:27 hoom kernel: [<ffffffff811997ae>] page_lock_anon_vma_read+0x5e/0x130
May 14 08:49:39 hoom kernel: [<ffffffff811997ae>] page_lock_anon_vma_read+0x5e/0x130
May 14 08:50:00 hoom kernel: [<ffffffff811997ae>] page_lock_anon_vma_read+0x5e/0x130
May 14 08:50:00 hoom kernel: [<ffffffff811997ae>] page_lock_anon_vma_read+0x5e/0x130
May 14 08:50:00 hoom kernel: [<ffffffff8108e595>] wq_worker_sleeping+0x15/0xa0
May 14 08:50:00 hoom kernel: [<ffffffff8156de97>] dump_stack+0x4c/0x6e
May 14 08:50:00 hoom kernel: [<ffffffff811997ae>] page_lock_anon_vma_read+0x5e/0x130
May 14 08:50:00 hoom kernel: [<ffffffff811997ae>] page_lock_anon_vma_read+0x5e/0x130
May 21 21:05:28 hoom kernel: [<ffffffff8119ac5e>] page_lock_anon_vma_read+0x5e/0x130
May 22 09:45:38 hoom kernel: [<ffffffff8119ac5e>] page_lock_anon_vma_read+0x5e/0x130
May 22 09:57:35 hoom kernel: [<ffffffff8119ac5e>] page_lock_anon_vma_read+0x5e/0x130
May 22 09:57:55 hoom kernel: [<ffffffff8119ac5e>] page_lock_anon_vma_read+0x5e/0x130
May 22 10:00:39 hoom kernel: [<ffffffff81571be3>] dump_stack+0x4c/0x6e
May 29 11:23:46 hoom kernel: [<ffffffff8119ac8e>] page_lock_anon_vma_read+0x5e/0x130
The user-space process that dies is not consistent:
journalctl >/tmp/journal ; grep Tainted /tmp/journal | less
Output:
Apr 06 11:00:02 hoom kernel: CPU: 2 PID: 2448 Comm: php Tainted: G O 3.19.2-1-ARCH #1
Apr 06 11:00:03 hoom kernel: CPU: 1 PID: 63 Comm: kswapd0 Tainted: G D O 3.19.2-1-ARCH #1
Apr 06 11:00:04 hoom kernel: CPU: 0 PID: 734 Comm: xfwm4 Tainted: G D O 3.19.2-1-ARCH #1
Apr 06 11:00:04 hoom kernel: CPU: 3 PID: 1135 Comm: thunderbird Tainted: G D O 3.19.2-1-ARCH #1
Apr 16 08:32:26 hoom kernel: CPU: 7 PID: 13402 Comm: Xvnc Tainted: G O 3.19.3-3-ARCH #1
Apr 16 13:49:42 hoom kernel: CPU: 4 PID: 26675 Comm: ssh Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 13:58:42 hoom kernel: CPU: 3 PID: 415 Comm: Xorg Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 14:00:00 hoom kernel: CPU: 1 PID: 24459 Comm: perl Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 14:02:29 hoom kernel: CPU: 5 PID: 551 Comm: snmpd Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 14:02:29 hoom kernel: CPU: 6 PID: 2 Comm: kthreadd Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 14:15:00 hoom kernel: CPU: 1 PID: 362 Comm: mysqld Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 14:15:48 hoom kernel: CPU: 3 PID: 732 Comm: gpg-agent Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 14:26:34 hoom kernel: CPU: 5 PID: 8598 Comm: panel-23-diskpe Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 14:44:00 hoom kernel: CPU: 2 PID: 25958 Comm: qemu-system-i38 Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 14:50:03 hoom kernel: CPU: 0 PID: 25403 Comm: rhythmbox Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 15:08:11 hoom kernel: CPU: 4 PID: 15301 Comm: qemu-dm Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 15:31:48 hoom kernel: CPU: 0 PID: 1533 Comm: qemu-dm Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 15:44:20 hoom kernel: CPU: 5 PID: 8595 Comm: panel-20-cpugra Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 16:04:01 hoom kernel: CPU: 2 PID: 1172 Comm: qemu-system-i38 Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 16:04:01 hoom kernel: CPU: 6 PID: 911 Comm: udisksd Tainted: G D O 3.19.3-3-ARCH #1
Apr 16 16:37:55 hoom kernel: CPU: 0 PID: 1685 Comm: qemu-dm Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:17:50 hoom kernel: CPU: 0 PID: 63 Comm: kswapd0 Tainted: G O 3.19.3-3-ARCH #1
Apr 26 09:17:50 hoom kernel: CPU: 7 PID: 11063 Comm: squid_redirect Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:17:50 hoom kernel: CPU: 4 PID: 2760 Comm: qemu-dm Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:17:50 hoom kernel: CPU: 5 PID: 11064 Comm: squid_redirect Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:17:50 hoom kernel: CPU: 7 PID: 435 Comm: Xorg Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:17:52 hoom kernel: CPU: 5 PID: 11056 Comm: DOM Worker Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:18:18 hoom kernel: CPU: 7 PID: 1515 Comm: rhythmbox Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:18:18 hoom kernel: CPU: 1 PID: 746 Comm: gpg-agent Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:18:19 hoom kernel: CPU: 4 PID: 579 Comm: snmpd Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:20:00 hoom kernel: CPU: 4 PID: 11076 Comm: php Tainted: G D O 3.19.3-3-ARCH #1
Apr 26 09:20:00 hoom kernel: CPU: 0 PID: 2591 Comm: qemu-dm Tainted: G D O 3.19.3-3-ARCH #1
May 11 09:38:10 hoom kernel: CPU: 0 PID: 17057 Comm: qemu-system-i38 Tainted: G O 4.0.1-1-ARCH #1
May 11 09:38:10 hoom kernel: CPU: 0 PID: 17057 Comm: qemu-system-i38 Tainted: G D O 4.0.1-1-ARCH #1
May 13 17:46:39 hoom kernel: CPU: 5 PID: 555 Comm: snmpd Tainted: G O 4.0.1-1-ARCH #1
May 14 08:45:00 hoom kernel: CPU: 7 PID: 63 Comm: kswapd0 Tainted: G O 4.0.1-1-ARCH #1
May 14 08:45:27 hoom kernel: CPU: 2 PID: 24007 Comm: qemu-dm Tainted: G D O 4.0.1-1-ARCH #1
May 14 08:49:39 hoom kernel: CPU: 1 PID: 567 Comm: snmpd Tainted: G D O 4.0.1-1-ARCH #1
May 14 08:50:00 hoom kernel: CPU: 3 PID: 117 Comm: kworker/3:1 Tainted: G D O 4.0.1-1-ARCH #1
May 14 08:50:00 hoom kernel: CPU: 1 PID: 22969 Comm: Xvnc Tainted: G D O 4.0.1-1-ARCH #1
May 14 08:50:00 hoom kernel: CPU: 3 PID: 117 Comm: kworker/3:1 Tainted: G D O 4.0.1-1-ARCH #1
May 14 08:50:00 hoom kernel: CPU: 3 PID: 117 Comm: kworker/3:1 Tainted: G D O 4.0.1-1-ARCH #1
May 14 08:50:00 hoom kernel: CPU: 7 PID: 24211 Comm: php Tainted: G D W O 4.0.1-1-ARCH #1
May 14 08:50:00 hoom kernel: CPU: 0 PID: 23626 Comm: panel-20-cpugra Tainted: G D W O 4.0.1-1-ARCH #1
May 21 21:05:28 hoom kernel: CPU: 1 PID: 28014 Comm: bacula-fd Tainted: G O 4.0.2-1-ARCH #1
May 22 09:45:38 hoom kernel: CPU: 0 PID: 589 Comm: snmpd Tainted: G O 4.0.2-1-ARCH #1
May 22 09:57:35 hoom kernel: CPU: 3 PID: 5667 Comm: qemu-dm Tainted: G D O 4.0.2-1-ARCH #1
May 22 09:57:55 hoom kernel: CPU: 1 PID: 4023 Comm: qemu-dm Tainted: G D O 4.0.2-1-ARCH #1
May 22 10:00:39 hoom kernel: CPU: 2 PID: 22103 Comm: java Tainted: G D O 4.0.2-1-ARCH #1
May 29 11:23:46 hoom kernel: CPU: 6 PID: 578 Comm: snmpd Tainted: G O 4.0.4-2-ARCH #1
diff of rmap.c
diff linux-3.18.6/mm/rmap.c linux-3.19.1/mm/rmap.c |less
Output:
26c26
< * mapping->i_mmap_mutex
> * mapping->i_mmap_rwsem
74a75,76
> anon_vma->degree = 1; /* Reference for first vma */
> anon_vma->parent = anon_vma;
190a193,194
> /* vma reference or self-parent link for new root */
> anon_vma->degree++;
238a243,250
> *
> * If dst->anon_vma is NULL this function tries to find and reuse existing
> * anon_vma which has no vmas and only one child anon_vma. This prevents
> * degradation of anon_vma hierarchy to endless linear chain in case of
> * constantly forking task. On the other hand, an anon_vma with more than one
> * child isn't reused even if there was no alive vma, thus rmap walker has a
> * good chance of avoiding scanning the whole hierarchy when it searches where
> * page is mapped.
258a271,282
>
> /*
> * Reuse existing anon_vma if its degree lower than two,
> * that means it has no vma and only one anon_vma child.
> *
> * Do not chose parent anon_vma, otherwise first child
> * will always reuse it. Root anon_vma is never reused:
> * it has self-parent reference and at least one child.
> */
> if (!dst->anon_vma && anon_vma != src->anon_vma &&
> anon_vma->degree < 2)
> dst->anon_vma = anon_vma;
259a284,285
> if (dst->anon_vma)
> dst->anon_vma->degree++;
282a309,311
> /* Drop inherited anon_vma, we'll reuse existing or allocate new. */
> vma->anon_vma = NULL;
>
290a320,323
> /* An existing anon_vma has been reused, all done then. */
> if (vma->anon_vma)
> return 0;
>
303a337
> anon_vma->parent = pvma->anon_vma;
313a348
> anon_vma->parent->degree++;
344c379,380
< if (RB_EMPTY_ROOT(&anon_vma->rb_root))
> if (RB_EMPTY_ROOT(&anon_vma->rb_root)) {
> anon_vma->parent->degree--;
345a382
> }
349a387,388
> if (vma->anon_vma)
> vma->anon_vma->degree--;
359a399
> BUG_ON(anon_vma->degree);
586c626,627
< pmde = ACCESS_ONCE(*pmd);
> pmde = *pmd;
> barrier();
1056c1097
< mem_cgroup_end_page_stat(memcg, locked, flags);
> mem_cgroup_end_page_stat(memcg, &locked, &flags);
1086c1127
< mem_cgroup_end_page_stat(memcg, locked, flags);
> mem_cgroup_end_page_stat(memcg, &locked, &flags);
1263c1304
< * we now hold anon_vma->rwsem or mapping->i_mmap_mutex.
> * we now hold anon_vma->rwsem or mapping->i_mmap_rwsem.
1383c1424
< pteval = ptep_clear_flush(vma, address, pte);
> pteval = ptep_clear_flush_notify(vma, address, pte);
1638c1679
< pgoff_t pgoff = page_to_pgoff(page);
> pgoff_t pgoff;
1645a1687
> pgoff = page_to_pgoff(page);
1679c1721
< pgoff_t pgoff = page_to_pgoff(page);
> pgoff_t pgoff;
1687c1729
< * so we can safely take mapping->i_mmap_mutex.
> * so we can safely take mapping->i_mmap_rwsem.
1693c1735,1737
< mutex_lock(&mapping->i_mmap_mutex);
>
> pgoff = page_to_pgoff(page);
> i_mmap_lock_read(mapping);
1714d1757
<
1716c1759
< mutex_unlock(&mapping->i_mmap_mutex);
> i_mmap_unlock_read(mapping);
In case there are some gurus reading this, here are all the Code lines from the crashes:
journalctl >/tmp/journal ; grep 'kernel: Code:' /tmp/journal | less
Output:
Apr 06 11:00:03 hoom kernel: Code: de 6f 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 f7 58 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 06 11:00:03 hoom kernel: Code: de 6f 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 f7 58 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 06 11:00:04 hoom kernel: Code: de 6f 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 f7 58 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 06 11:00:04 hoom kernel: Code: de 6f 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 f7 58 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 08:32:26 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 13:49:42 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 13:58:42 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 14:00:00 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 14:02:29 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 14:15:00 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 14:15:48 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 14:26:34 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 14:44:00 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 14:50:03 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 15:08:11 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 15:31:48 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 15:44:20 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 16:04:01 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 16:04:02 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 16 16:37:55 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:17:50 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:17:50 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:17:50 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:17:50 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:17:50 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:17:52 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:18:18 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:18:18 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:18:19 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:20:00 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
Apr 26 09:20:00 hoom kernel: Code: be 70 4a 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 d7 59 4a 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 11 09:38:10 hoom kernel: Code: 5b 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 48 8b 87 a8 00 00 00 55 48 89 e5 48 2b 70 68 48 8b 40 60 5d 48 c1 ee 0c <48> 8b 04 f0 c3 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 66 66
May 13 17:46:39 hoom kernel: Code: 3e 54 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 87 3d 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 14 08:45:00 hoom kernel: Code: 3e 54 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 87 3d 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 14 08:45:27 hoom kernel: Code: 3e 54 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 87 3d 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 14 08:49:39 hoom kernel: Code: 3e 54 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 87 3d 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 14 08:50:00 hoom kernel: Code: 3e 54 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 87 3d 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 14 08:50:00 hoom kernel: Code: 3e 54 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 87 3d 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 14 08:50:00 hoom kernel: Code: 00 48 89 e5 5d 48 8b 40 c8 48 c1 e8 02 83 e0 01 c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 48 8b 87 20 05 00 00 55 48 89 e5 <48> 8b 40 d8 5d c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90
May 14 08:50:00 hoom kernel: Code: 3e 54 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 87 3d 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 14 08:50:00 hoom kernel: Code: 3e 54 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 87 3d 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 21 21:05:28 hoom kernel: Code: 2e 90 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 77 79 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 22 09:45:38 hoom kernel: Code: 2e 90 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 77 79 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 22 09:57:35 hoom kernel: Code: 2e 90 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 77 79 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 22 09:57:55 hoom kernel: Code: 2e 90 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 77 79 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7
May 29 11:23:46 hoom kernel: Code: 6e bf 4b 00 48 83 c4 18 5b 5d c3 0f 1f 80 00 00 00 00 48 89 45 e8 e8 b7 a8 4b 00 48 8b 45 e8 eb d8 90 66 66 66 66 90 55 48 89 e5 <48> 8b 07 48 89 c2 48 83 c2 01 7e 07 f0 48 0f b1 17 75 f0 48 f7

Thanks for the quick reply. To answer your questions:
Yes, I've been running pacman -Syu every now and again, including kernel updates. You can see the info hidden buried down in end note 5, but here's the journal log info more clearly:
Jan 24 20:52:32 hoom kernel: Linux version 3.18.2-2-ARCH (builduser@tobias) (gcc version 4.9.2 20141224 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Jan 9 07:37:51 CET 2015
Mar 14 13:06:26 hoom kernel: Linux version 3.18.6-1-ARCH (builduser@tobias) (gcc version 4.9.2 20141224 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015
Apr 06 10:14:39 hoom kernel: Linux version 3.19.2-1-ARCH (builduser@tobias) (gcc version 4.9.2 20150304 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015
Apr 08 22:52:57 hoom kernel: Linux version 3.19.3-3-ARCH (builduser@tobias) (gcc version 4.9.2 20150304 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST 2015
May 09 21:35:07 hoom kernel: Linux version 4.0.1-1-ARCH (builduser@tobias) (gcc version 5.1.0 (GCC) ) #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015
May 14 20:52:23 hoom kernel: Linux version 4.0.2-1-ARCH (builduser@tobias) (gcc version 5.1.0 (GCC) ) #1 SMP PREEMPT Thu May 7 06:47:54 CEST 2015
May 23 22:42:18 hoom kernel: Linux version 4.0.4-2-ARCH (builduser@foutrelis) (gcc version 5.1.0 (GCC) ) #1 SMP PREEMPT Fri May 22 03:05:23 UTC 2015
I have an AMD processor (vendor_id: AuthenticAMD, cpu family: 21 (0x15), model: 2, model name: AMD FX(tm)-8350 Eight-Core Processor, stepping: 0, microcode: 0x6000822). It looks like microcode updates from 0x06000822 to 0x06000832 have been failing:
Jan 03 21:41:05 hoom kernel: microcode: CPU0: patch_level=0x06000822
Jan 03 21:41:05 hoom kernel: microcode: CPU1: patch_level=0x06000822
Jan 03 21:41:05 hoom kernel: microcode: CPU2: patch_level=0x06000822
Jan 03 21:41:05 hoom kernel: microcode: CPU3: patch_level=0x06000822
Jan 03 21:41:05 hoom kernel: microcode: CPU4: patch_level=0x06000822
Jan 03 21:41:05 hoom kernel: microcode: CPU5: patch_level=0x06000822
Jan 03 21:41:05 hoom kernel: microcode: CPU6: patch_level=0x06000822
Jan 03 21:41:05 hoom kernel: microcode: CPU7: patch_level=0x06000822
Jan 03 21:41:05 hoom kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
Jan 03 21:41:05 hoom kernel: microcode: CPU0: update failed for patch_level=0x06000832
Jan 03 21:41:05 hoom kernel: microcode: CPU1: update failed for patch_level=0x06000832
Jan 03 21:41:05 hoom kernel: microcode: CPU2: update failed for patch_level=0x06000832
Jan 03 21:41:05 hoom kernel: microcode: CPU3: update failed for patch_level=0x06000832
Jan 03 21:41:05 hoom kernel: microcode: CPU4: update failed for patch_level=0x06000832
Jan 03 21:41:05 hoom kernel: microcode: CPU5: update failed for patch_level=0x06000832
Jan 03 21:41:05 hoom kernel: microcode: CPU6: update failed for patch_level=0x06000832
Jan 03 21:41:05 hoom kernel: microcode: CPU7: update failed for patch_level=0x06000832
Since Jan 18th, I have seen no more messages like above. The only microcode lines I see in the journal are:
Jan 18 16:21:15 hoom kernel: [drm] Loading CAICOS Microcode
but I assume they're not relevant and are for the graphics card:
[ashley@hoom ~]$ lspci | grep -i caicos
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
I have the package linux-firmware installed (version 20150511.8e18132-1) and the MD5 checksums for all the files in /usr/lib/firmware/amd-ucode/ match the checksums from the files I downloaded from http://www.amd64.org/microcode.html.
I'll look forther into getting the microcode updated.

IPod touch random crashing

I just upgraded from a 3G 40GB iPod to a brand spankin' new 16Gb iPod touch, and I'm noticing some random weirdness with it. First a few details:
*- At this moment I have 969 songs, 1 video, and 4 photos loaded on my iPod touch, leaving 3.9GB free.*
*- I bought the iPod last Sunday, and it came loaded with firmware 1.1.1.*
*- This morning I updated the iPod to firmware 1.1.2 with no issues.*
Here's what I've noticed so far:
a) If you create a new playlist directly on the ipod itself (using the On The Go list), it sometimes randomly crashes and resets back to the home screen. I'll be sorting the music list by artist name, and it usually happens when I tap on their name, followed by the name of the album/CD. One time when this happened I noticed that the name of a song was "blinking" (best way I can describe it). The text was "blinking" left and right, followed by the ipod resetting itself back to the home screen.
b) I've noticed that after a while, tracks that were were encoded directly from a CD with Apple Lossless Compression lose the ability to seek using the seek bar (tap once on the screen while a song is playing to display it). The pointer on the bar will move to the desired location, but the song keeps playing at it's present location. Tapping the last track/next track arrows doesn't do anything either (you'd need to tap them twice). Doing a reset by holding down the power button on the top of the player and sliding the slider fixes it for a short while. I haven't tried this yet with the 1.1.2 firmware installed, so I don't know if this particular bug has been squashed.
c) I've had it crash once while selecting a song from the artists playlist. Hasn't happened again yet since updating to 1.1.2.
d) I have had random crashes using the youTube feature. I haven't tried it yet with firmware 1.1.2 though, so I do not know if this bug has been fixed yet either.
Overall I like the iPod touch. I like the features it has and it's a nice replacement to my dead 3G iPod. What I'm not liking is now unrefined the firmware seems to be. Everything I'm seeing points to a firmware problem Vs. a hardware problem.
I would greatly appreciate it if someone from Apple's ipod dev team would look into the issue. I do not want or need a personalized reply; rather think of this posting as a bug report. I have been allowing iTunes to send crash reports, but I have no way of knowing if this exact error is being reported.

Well, on my way home today I was using my iPod in my car (I have it directly connected to my stereo system using a Belkin Auto Kit (which, by the way works fine with the iPod Touch)), and I noticed something else.
Initially I thought the issue with the seek bar not working was limited to songs I had ripped from CD's in my collection using ALC compression. It looks like it's also affecting songs I have downloaded from the iTunes store too.
I tapped the rewind button (the "|<<" button), and it wouldn't rewind the song back to the beginning. So I tapped it again, and it went to the previous song. I happened to be pulling into my driveway so I stopped the car, picked up the iPod and started playing with it. Sure enough the problem came back. I tried seeking using the slider. No go. the "|<<" and ">>|" buttons weren't working right again either.
I unplugged the iPod from the auto adapter and gave it another go. Same issue.
That was about 2 hours ago. I just tried using the iPod a few minutes ago and it's still doing it.
I just did a soft reset a moment ago by holding down the power button and then powering down the iPod. It's working fine again.
In four years I think the most I ever reset my older 3G 40GB iPod was around 8 to 10 times TOPS. I'm well past that with the iPod touch, and I haven't owned it for more than a week.
I think Safari has crashed on me once or twice, but to be honest I cut that app a lot of slack. There's a lot of badly designed web sites out there that have even crashed & locked up my Palm Treo 700WX phone to the point I needed to do a reset on it. I'm being a bit more critical over the issues I'm finding because they're part of the basic functionality of the device.
Simply put, the issues I'm experiencing are small and annoying, but they should have been caught before release. Granted things sometimes slip through the cracks, but if you consider just how visible the issue is, it's even more surprising that it wasn't caught in testing (hopefully it was tested before release?......).

Premiere Pro random crashing since update to 2014.2

Been working on the SAME big project over 18 months, in Pr Pro CC, 2014, working on the SAME PC:
Win 7 SP1 pro 64bit, i7-3770K, 32GB fast memory (25.7 available for Pr), Intel HD 4000 graphics on Asus motherboard with 30" NEC Multisync screen at 2560 x 1600 (same as for years)
42GB free on my SSD drive C: and 54GB free on my SSD drive S: for preview files, 24GB free on my SSD drive T: for caching files. Project files etc stored on a normal hard drive F: (for Files!) 1.25TB free.
NOW last update to 2014.2 and I get constant RANDOM crashes (Windows encountered a fault and had to close this program) despite updating graphics driver and trying different settings in preferences, use mercury etc. No particular action causes it - sometimes I am just watching it play a sequence and it just stops. Though of course it may be rendering the last edit at the time.
Sometimes it runs for all of 15 mins and I think the problem has sorted then it goes again and I have to restart the project, find where I was and re-do my last edits. If I remember to press Ctrl-S very frequently (every few seconds) it seems to run for a while then I forget for 5 mins and it crashes.
Grrrr what did you do to the latest version, Adobe?? I need to get this project finally finished in a hurry.... I wish I had not updated the program! Of course I cannot go back as it says the saved copy is now incompatible with earlier Pr Pro versions.
I then tried running a previous version at the same time, as simonray suggested in his post - it worked! So I am able to continue as normal provided I do this stupid bodge fix.
So it really is down to Adobe as it is the same project, same PC, just different version update. You did something to a great, stable, program that made it unstable, Adobe...
To ANSWER RAMEEZ from previous thread:
A variety of issues can cause PPRO to crash:
a problem with the Preferences, or some other pref-related file in the Profile-<USERNAME> bin. >> DIDN'T CHANGE ANYTHING since 1½ years running previous PrPro versions on SAME PROJECT on SAME PC
the graphics driver Checked for latest version - didn't stop the crashing
third-party plug-ins - don't have any
a problem with the cache files. I am using the same 2 x SSD I have been using for years for autosave and caching. 54GB free space / 24GB free space (current cache in place)
a problem with the project file (if you're loading a project...) Doesn't apply
the Preferences files be set to read-only How would that happen? Never happened before on any other update and I can change it.
the user not having administrator rights Only one user on PC since installation, full rights
a conflict/incompatibility with some OS setting Haven't changed anything
a problem on the licensing/authentication side. I'm signed up to full Adobe CC. Everything else works, Ps, Lr, Id ...
A log file might help identify the cause of the crash. Please right-click 'My Computer', select "Manage," look under 'Event Viewer->Windows Logs->Application' to see if there's an event there from Premiere Pro. If so, copy the contents of that log and paste them here.
>>>>>>>>>>>>>>
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: VideoFilterHost.dll, version: 8.2.0.65, time stamp: 0x5486bf85
Exception code: 0xc0000005
Fault offset: 0x000000000006d692
Faulting process id: 0x19d0
Faulting application start time: 0x01d022d29c3e2d43
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\VideoFilterHost.dll
Report Id: 1097ced4-8ec8-11e4-aaaf-08606e6e6383
<<<<<<<<<<<<<<<
Thanks,
Rameez

Problem Solved! (with a small catch)
While searching crashing issues I came across this thread,"Premiere Pro random crashing since update to 2014.2"
Marc_Lec Answered (and I paraphrase here)"...I had the same problem and this is what I did. In 'Preferences Memory' I increased the memory reserved for other application to at least half the installed and changed the optimize render from 'performance' to 'memory."
Thank You Marc_Lec for what has been a game changer for me since my last computer and the beginning of PremiereCC problems.
I changed my Memory reserved for Other Applications from the default 7gigs to 1/2 of my approx.31 available Gigs = 16Gigs. Viola!
No more crashing what-so-ever!
I still have to purchase an older GTX 980 graphics card to take advantage of Adobe's approved code to utilize X=Cuda Cores and GPU, but I think I'll hang onto my new TitanX, in hopes that Adobe will write code and approve it someday in the near future.
Now why doesn't Adobe say this officially about Memory Settings? (I don't know maybe they do and I missed I somewhere)
Mine and probably many peoples computers problems here on this board may be attributed to a simple Memory adjustment, because the computer needs more than 7Gigs to run itself, not to mention Premiere.

FCP HD Render problems... lots of random crashing... help!!

Similar Messages

Maybe you are looking for