External Table - possible bug related to record size and total bytes in fil

I have an External Table defined with fixed record size, using Oracle 10.2.0.2.0 on HP/UX. At 279 byte records (1 or more fields, doesn't seem to matter), it can read almost 5M bytes in the file (17,421 records to be exact). At 280 byte records, it can not, but blows up with "partial record at end of file" - which is nonsense. It can read up to 3744 records, just below 1,048,320 bytes (1M bytes). 1 record over that, it blows up.
Now, If I add READSIZE and set it to 1.5M, then it works. I found this extends further, for instance 280 recsize with READSIZE 1.5M will work for a while but blows up on 39M bytes in the file (I didn't bother figuring exactly where it stops working in this case). Increasing READSIZE to 5M works again, for 78M bytes in file. But change the definition to have 560 byte records and it blows up. Decrease the file size to 39M bytes and it still won't work with 560 byte records.
Anyone have any explanation for this behavior? The docs say READSIZE is the read buffer, but only mentions that it is important to the largest record that can be processed - mine are only 280/560 bytes. My table definition is practically taken right out of the example in the docs for fixed length records (change the fields, sizes, names and it is identical - all clauses the same).
We are going to be using these external tables a lot, and need them to be reliable, so increasing READSIZE to the largest value I can doesn't make me comfortable, since I can't be sure in production how large an input file may become.
Should I report this as a bug to Oracle, or am I missing something?
Thanks,
Bob

I have an External Table defined with fixed record size, using Oracle 10.2.0.2.0 on HP/UX. At 279 byte records (1 or more fields, doesn't seem to matter), it can read almost 5M bytes in the file (17,421 records to be exact). At 280 byte records, it can not, but blows up with "partial record at end of file" - which is nonsense. It can read up to 3744 records, just below 1,048,320 bytes (1M bytes). 1 record over that, it blows up.
Now, If I add READSIZE and set it to 1.5M, then it works. I found this extends further, for instance 280 recsize with READSIZE 1.5M will work for a while but blows up on 39M bytes in the file (I didn't bother figuring exactly where it stops working in this case). Increasing READSIZE to 5M works again, for 78M bytes in file. But change the definition to have 560 byte records and it blows up. Decrease the file size to 39M bytes and it still won't work with 560 byte records.
Anyone have any explanation for this behavior? The docs say READSIZE is the read buffer, but only mentions that it is important to the largest record that can be processed - mine are only 280/560 bytes. My table definition is practically taken right out of the example in the docs for fixed length records (change the fields, sizes, names and it is identical - all clauses the same).
We are going to be using these external tables a lot, and need them to be reliable, so increasing READSIZE to the largest value I can doesn't make me comfortable, since I can't be sure in production how large an input file may become.
Should I report this as a bug to Oracle, or am I missing something?
Thanks,
Bob

Similar Messages

  • Get Total DB size , Total DB free space , Total Data & Log File Sizes and Total Data & Log File free Sizes from a list of server

    how to get SQL server Total DB size , Total DB free space , Total Data  & Log File Sizes and Total Data  & Log File free Sizes from a list of server 

    Hi Shivanq,
    To get a list of databases, their sizes and the space available in each on the local SQL instance.
    dir SQLSERVER:\SQL\localhost\default\databases | Select Name, Size, SpaceAvailable | ft -auto
    This article is also helpful for you to get DB and Log File size information:
    Checking Database Space With PowerShell
    I hope this helps.

  • Is it possible to change the font size and weight in an ADF table?

    Is it possible to change the font size and weight in an ADF table? I have tried to change the various font size and weight settings for a table and its columns and they seem to have no effect on the font size or weight in a table row.

    You would use skinning to modify font-size & weight for the table.
    In addition to the link suggested by Vinod,
    Take a look at http://biemond.blogspot.com/2009/01/adf-skinning-in-jdeveloper-11g.html
    Thanks,
    Navaneeth

  • How is it posible to get the File name, size and type from a File out the H

    How is it posible to get the File name, size and type from a File out the HttpServletRequest. I want to upload a File from a client and save it on a server with the client name. I want to conrole before saving the name, type and size of the file.How is it posible to get the File name, size and type from a File out the HttpServletRequest.
    form JSP
    <form name="form" method="post" action="procesuploading.jsp" ENCTYPE="multipart/form-data">
    File: <input type="file" name="filename"/
    Path: <input type="text" readonly="" name="path" value="c:"/
    Saveas: <input type="text" name="saveas"/>
    <input name="submit" type="submit" value="Upload" />
    </form>
    proces JSP
    <%@ page language="java" %>
    <%@ page import="java.util.*" %>
    <%@ page import="FileUploadBean" %>
    <jsp:useBean id="TheBean" scope="page" class="FileUploadBean" />
    <%
    TheBean.doUpload(request);
    %>
    BEAN
    import java.io.*;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletResponse;
    import javax.servlet.ServletInputStream;
    public class FileUploadBean {
    public void doUpload(HttpServletRequest request) throws IOException
              String melding = "";
              String filename = request.getParameter("saveas");
              String path = request.getParameter("path");
              PrintWriter pw = new PrintWriter(new BufferedWriter(new FileWriter("test.java")));
              ServletInputStream in = request.getInputStream();
              int i = in.read();
              System.out.println("filename:"+filename);
              System.out.println("path:"+path);
              while (i != -1)
                   pw.print((char) i);
                   i = in.read();
              pw.close();
    }

    Thanks it works great.
    Here an excample from my code
    import org.apache.commons.fileupload.*;
    public class FileUploadBean extends Object implements java.io.Serializable{
    String foutmelding = "geen";
    String path;
    String filename;
    public boolean doUpload(HttpServletRequest request) throws IOException
         try
         // Create a new file upload handler
         FileUpload upload = new FileUpload();
         // Set upload parameters
         upload.setSizeMax(100000);
         upload.setSizeThreshold(100000000);
         upload.setRepositoryPath("/");
         // Parse the request
         List items = upload.parseRequest(request);
         // Process the uploaded fields
         Iterator iter = items.iterator();
         while (iter.hasNext())
         FileItem item = (FileItem) iter.next();
              if (item.isFormField())
                   String stringitem = item.getString();
         else
              String filename = "";
                   int temp = item.getName().lastIndexOf("\\");
                   filename = item.getName().substring(temp,item.getName().length());
                   File bestand = new File(path+filename);
                   if(item.getSize() > SizeMax && SizeMax != -1){foutmelding = "bestand is te groot.";return false;}
                   if(bestand.exists()){foutmelding ="bestand bestaat al";return false;}
                   FileOutputStream fOut = new FileOutputStream(bestand);     
                   BufferedOutputStream bOut = new BufferedOutputStream(fOut);
                   int bytesRead =0;
                   byte[] data = item.get();
                   bOut.write(data, 0 , data.length);     
                   bOut.close();
         catch(Exception e)
              System.out.println("er is een foutontstaan bij het opslaan de een bestand "+e);
              foutmelding = "Bestand opsturen is fout gegaan";
         return true;
         }

  • Is it possible to convert Java to EXE and run this EXE file without any JRE

    hello friends
    I have GCC/GCJ for windows but dont know how to work with it... it creates file with .o extension but i m not able to create .exe from that... i installed mingw for that also .. unsuccessful ...
    tell me the solution for it... i want to generate machine dependent exe from java file...on the web i ve seen that GCC/GCJ is used on linux platform..not cleared properly..
    Again i m writing my question
    Is it possible to convert Java to EXE and run this EXE file without any JRE if yes then how... tell me the procedure to do that...

    Vipul wrote:
    Its software now hardware .... some times u need these things ...anyway do u ve solution for my questionSo what? By creating a native executable you are restricting the program to the OS for which that native executable was made, just like removing the engine from a car restricts driving to downhill only. So like the I said, the principle remains the same, "Why would you want to?"
    I am asking you, truthfully, why do you feel the need to negate the largest advantage of using Java by creating a native executable from it?
    What is your rationale?
    I can pretty much guarantee there is a much better way of achieving your wish without "removing the engine".

  • Please fix the Robohelp bug related to supporting underscores (_) in the help files (*.chm)

    There are 10 module specific projects. Further map IDs are assigned in all the 10 module projects to have context sensitivity. These are merged into a single project to generate the entire help file. The output for the project is html help (.chm).
    Initially, we generated the html help and integrated with the application. When tested (pressed F1) the correct topic is displayed but with the ToC for that module and not the entire help. 
    Solution: I followed the steps mentioned in the following thread that I came across on Adobe forum. 
    http://forums.adobe.com/message/240496#240496
    But the solution didn’t work as expected, Further investigation showed that since the output file name had underscore (Module1_EN.chm to denote the language), the solution didn’t work.  Hence I removed the ‘underscore (_)’ from the output file name and generated the output again. This time the solution worked.
    Please refer below the steps for generating the output.
    Steps:
    Generated output (chm) for all the modules.  I had to make sure that the output file name does not contain any ‘underscore (_)’ as this caused the problem when generated the help file.  
    In the main help project (which is an empty container), merged all the projects using Robohelp’s Merged Project functionality.  While merging, I first created empty Book and then merged the project within that book.
    For example, Book1 will contain Module1.chm, Book2 will contain Module2.chm and so on.
    Added window definitions using Project Setup -> New Window. Also added reference to main ToC here by clicking Advanced Properties. (Table of Contents: Main.hhc)
    Selected the above created window while generating the output (Single source layouts -> html help Layout -> Properties).
    Generated the html output for the entire project (Main.chm).
    Decompile the ‘Main.chm’ and extracted the ToC file ‘Main.hhc’.
    For each module project, imported ‘Main.hhc’ as a Baggage File, created window definitions same as the Main project and with reference to ‘Main.hhc’.
    Again generated html output for all the modules.
    Tested CSH for the project. The correct topic displayed with the entire ToC.
    Best regards,
    /Vikas

    You need to post a bug report to get Adobe's attention. This is a user to user forum. Please follow this link.
    http://www.Adobe.com/cfusion/mmform/index.cfm?name=wishform&product=38
    Not sure but I believe it may be a bug in the Microsoft Help Compiler over which Adobe have no control. Microsoft last updated in 2004. Good luck!
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Possible bug: Saving array with extended and double precision to spreadshee​t

    If one concatenates a double precision array and an extended precision array with the "build array" vi and then saves using "Write to Spreadsheet File" vi any digits to the right of the decimal place are set to zero in the saved file. This happens regardless of the format signifier input (e.g. %.10f) to the  "Write to Spreadsheet File" vi.
    I am on Vista Ultimate 32 bit and labview 9.0
    This is a possible bug that is easily circumvented by converting to one type before combining arrar to a spreadsheet. Nonetheless, it is a bug and it cost me some time.
    Solved!
    Go to Solution.
    Attachments:
    Spreadsheet save bug.vi ‏9 KB

    Hi JL,
    no, it's not a bug - it's a feature
    Well, if you would look more closely you would recognize the "Save to Spreadsheet" as polymorphic VI. As this polymorphic VI doesn't support EXT numbers internally (it only supports DBL, I64 and String) LabVIEW chooses the instance with most accuracy: I64 (I64 has 64 bits precision, DBL only 53...). So your options are:
    - set the instance to use as DBL (by right-click and "Select type...")
    - make a copy of this VI, save it with a different name and make it support EXT numbers (don't rework the polymorphic VI as you would break compatibility with other LV installations or future revisions)
    And yes, those coercion dots always signal some conversions - you should atleast check what's going on there...
    Message Edited by GerdW on 05-21-2010 10:01 PM
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • 3.1EA1 bug: Exporting 300K records to a .xls or .xlsx file

    Hello:
    Exporting a large query result (300K records) into a .xls or .xlsx file will cause SQL Developer to hang. On some occurences, SQL Developer will not hang, but the file created is empty.
    Thanks,
    Adrian

    Hi Adrian,
    This is a known issue and even documented in the SQL Developer Help. Here are a couple of prior threads discussing it. To summarize their advice, either export to a csv file instead, or increase the Java VM's Xmx limit:
    Re: Export to Excel Hangs
    Re: the developer 3 crashed,when i exported the data out xls ,why?
    Regards,
    Gary
    SQL Developer Team

  • New number of posts bug(?) + question; no #100, and total # of posts vary

    New number of posts bug(?) + question; no number 100, and total number of posts vary
    Intrigued by Tuttle's new attempt to join Niel's old habit to keep his own total number of posts count, I went and start counting my posts since the New Discussions. Because I saved my latest Old Discussions Post-and-Points info, I can see what are the previously-still-online ones (the pre- 14-Nov-2005 01:31 GMT ones), and I know exactly what was my "real" total number of posts before 14-Nov-2005 (2446).
    My New Discussions posts number however, is quite uncertain.
    Firstly, when I use the "My Posts" link on the right, then clicking on and on on the "Next" link,
    my "Viewing 91-100 of 586 -- Pages" shows 91-99 instead of 91-100
    (= should show 10 posts, shows 9 posts)
    then I go on clicking Next Next Next, and I see the same missing counts happen elsewhere:
    my posts number 100, 259, 260, 370, 390, 520, 558, 559, 560, 578, 579, and 580 are missing too.
    Note that I wouldn't bother doing all this, and I would have thought it's just very old posts that are automatically deleted like in the Old Discussions,
    BUT,
    the problem is that when I choose to see all my posts together on the same page
    (by using the start=0&range=600 suffix in the URL)
    I get a total number of posts that is different (570).
    A third way to quickly see all posts without having to load too big page
    (using the start=0&range=300 suffix in the URL then only one "Next" click)
    shows yet another, different again, number of total posts (573).
    And my "official" total number of posts is (586).
    Dear HOSTS,
    - If this can be used as a bug report to fix a counting problem, glad to help.
    - If there is no bug, I have two(+) questions then:
    1) Was my post number 100 deleted?
    (should be around 27-Nov-2005 18:00 GMT)
    Also:
    I thought the Total Posts number that we see in "My Public Profile" or under the avatar in each post (586), was only the number of posts still online.
    - if it is the case, then there are no automatically deleted old posts anymore?
    - if old posts are automatically deleted like before, this number should vary?
    - if it doesn't vary (it just grows by one per new post), AND at the same time old posts are actually automatically deleted,
    it has to show the "real" total number of posts then,
    (as it is now, a total starting from the Old-Discussions-still-online-posts, it makes no sense),
    that is,
    the total posts in the New Discussions PLUS the total posts since first registration in the Old Discussions.
    So,
    2) What does it show exactly?
    Thanks again for all the great work!
    Axl
    220? 221?

    Thank you Andreas,
    Your confirmation about the "post #100 bug" does help.
    "As for your other missing posts - I guess Tuttle's assessment that they might be deleted is probably right..."
    Yes, that makes sense and that's what I'm trying to figure in my OP, but then,
    after I posted my "#221/2667 post" (11-Dec-2005 21:51 GMT), my originally missing #
    259, 260, 370, 390, 520, 558, 559, 560, 578, 579, and 580
    should have become
    260, 261, 371, 391, 521, 559, 560, 561, 579, 580, and 581
    right? (forget the #100: this one we know for sure it's a bug)
    Or if the software counts them from the first (now that would have been a good start) instead of starting from the most recent,
    they should become
    258, 259, 369, 389, 519, 557, 558, 559, 577, 578, and 579
    Well, that's not what happened. Now the missing # are
    259, 260, 370, 390, 400, 520, 559, 560, 570, 579, and 580
    (in addition to the same #100) (#558 and 578 not missing anymore).
    As you can see, there is no logic:
    It doesn't work as a simple numerotation of StillOnlinePosts, no matter the order
    (otherwise there would simply be a straight count from 1 to 575 (=587-12).
    It looks indeed like it shows which old posts are being automatically deleted. That the numbers are quite the same would simply show that the old posts dates were so close, of course they are deleted (six months later) almost at the same time,
    BUT,
    if it was the case, there would never be LESS deleted posts between two StillOnlinePosts, like it happens for example between my StillOnlinePosts #557 and #561.
    Please note: of course I stick to the same method to make all my counts. Not manually modifying the URL, just using the default Next-Next-Next- clicking...
    Modifying URL would add yet more differences in the differences!..
    Dear Hosts,
    Too bad it doesn't help looking yourself at my "My Posts", as everything changes each time I'm adding a reply somewhere.
    Perhaps a good way to troubleshoot this would be to start from a very simple basis:
    --> "name" the posts with a number, starting from the oldest.
    This way, for example my "#1" post (11-Dec-2005 21:51 GMT in this thread) would be named "221" in the New Discussions, or "2667" if you start from my Registration date.
    At the moment, it is very difficult to figure what fault comes from the "#100 post bug" and what fault comes from another possible counting bug...
    Then the New Discussions "fluctuating" refreshing delay too, possibly messes the counts...
    Thanks!
    Axl
    223/2669

  • A possible bug related to the Cisco ASA "show access-list"?

    We encountered a strange problem in our ASA configuration.
    In the "show running-config":
    access-list inside_access_in remark CM000067 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:http_access
    access-list inside_access_in remark CM000458 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:https_access
    access-list inside_access_in remark test 11111111111111111111111111 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security
    access-list inside_access_in extended permit tcp host 1.1.1.1 host 192.168.20.86 eq 81 log
    access-list inside_access_in remark CM000260 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:netbios-dgm
    access-list inside_access_in remark CM006598 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:netbios-ns
    access-list inside_access_in remark CM000220 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:netbios-ssn
    access-list inside_access_in remark CM000223 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:tcp/445
    access-list inside_access_in extended permit tcp 172.31.254.0 255.255.255.0 any eq www log
    access-list inside_access_in extended permit tcp 172.31.254.0 255.255.255.0 any eq https log
    access-list inside_access_in extended permit udp 172.31.254.0 255.255.255.0 any eq netbios-dgm log
    access-list inside_access_in extended permit udp 172.31.254.0 255.255.255.0 any eq netbios-ns log
    access-list inside_access_in extended permit tcp 172.31.254.0 255.255.255.0 any eq netbios-ssn log
    access-list inside_access_in extended permit tcp 172.31.254.0 255.255.255.0 any eq 445 log
    access-list inside_access_in remark CM000280 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:domain
    access-list inside_access_in extended permit tcp object 172.31.254.2 any eq domain log
    access-list inside_access_in extended permit udp object 172.31.254.2 any eq domain log
    access-list inside_access_in remark CM000220 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:catch_all
    access-list inside_access_in extended permit ip object 172.31.254.2 any log
    access-list inside_access_in remark CM0000086 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:SSH_internal
    access-list inside_access_in extended permit tcp 172.31.254.0 255.255.255.0 interface inside eq ssh log
    access-list inside_access_in remark CM0000011 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:PortRange
    access-list inside_access_in extended permit object TCPPortRange 172.31.254.0 255.255.255.0 host 192.168.20.91 log
    access-list inside_access_in remark CM0000012 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:FTP
    access-list inside_access_in extended permit tcp object inside_range range 1024 45000 host 192.168.20.91 eq ftp log
    access-list inside_access_in remark CM0000088 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:PortRange
    access-list inside_access_in extended permit ip 192.168.20.0 255.255.255.0 any log
    access-list inside_access_in remark CM0000014 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:DropIP
    access-list inside_access_in extended permit ip object windowsusageVM any log
    access-list inside_access_in extended permit ip any object testCSM-object
    access-list inside_access_in extended permit ip 172.31.254.0 255.255.255.0 any log
    access-list inside_access_in remark CM0000065 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:IP
    access-list inside_access_in extended permit ip host 172.31.254.2 any log
    access-list inside_access_in remark CM0000658 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security
    access-list inside_access_in extended permit tcp host 192.168.20.95 any eq www log
    In the "show access-list":
    access-list inside_access_in line 1 remark CM000067 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:http_access
    access-list inside_access_in line 2 remark CM000458 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:https_access
    access-list inside_access_in line 3 remark test 11111111111111111111111111 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security
    access-list inside_access_in line 4 extended permit tcp host 1.1.1.1 host 192.168.20.86 eq 81 log informational interval 300 (hitcnt=0) 0x0a                                                           3bacc1
    access-list inside_access_in line 5 remark CM000260 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:netbios-dgm
    access-list inside_access_in line 6 remark CM006598 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:netbios-ns
    access-list inside_access_in line 7 remark CM000220 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:netbios-ssn
    access-list inside_access_in line 8 remark CM000223 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:tcp/445
    access-list inside_access_in line 9 extended permit tcp 172.31.254.0 255.255.255.0 any eq www log informational interval 300 (hitcnt=0) 0x06                                                           85254a
    access-list inside_access_in line 10 extended permit tcp 172.31.254.0 255.255.255.0 any eq https log informational interval 300 (hitcnt=0) 0                                                           x7e7ca5a7
    access-list inside_access_in line 11 extended permit udp 172.31.254.0 255.255.255.0 any eq netbios-dgm log informational interval 300 (hitcn                                                           t=0) 0x02a111af
    access-list inside_access_in line 12 extended permit udp 172.31.254.0 255.255.255.0 any eq netbios-ns log informational interval 300 (hitcnt                                                           =0) 0x19244261
    access-list inside_access_in line 13 extended permit tcp 172.31.254.0 255.255.255.0 any eq netbios-ssn log informational interval 300 (hitcn                                                           t=0) 0x0dbff051
    access-list inside_access_in line 14 extended permit tcp 172.31.254.0 255.255.255.0 any eq 445 log informational interval 300 (hitcnt=0) 0x7                                                           b798b0e
    access-list inside_access_in line 15 remark CM000280 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:domain
    access-list inside_access_in line 16 extended permit tcp object 172.31.254.2 any eq domain log informational interval 300 (hitcnt=0) 0x6c416                                                           81b
      access-list inside_access_in line 16 extended permit tcp host 172.31.254.2 any eq domain log informational interval 300 (hitcnt=0) 0x6c416                                                           81b
    access-list inside_access_in line 17 extended permit udp object 172.31.254.2 any eq domain log informational interval 300 (hitcnt=0) 0xc53bf                                                           227
      access-list inside_access_in line 17 extended permit udp host 172.31.254.2 any eq domain log informational interval 300 (hitcnt=0) 0xc53bf                                                           227
    access-list inside_access_in line 18 remark CM000220 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:catch_all
    access-list inside_access_in line 19 extended permit ip object 172.31.254.2 any log informational interval 300 (hitcnt=0) 0xd063707c
      access-list inside_access_in line 19 extended permit ip host 172.31.254.2 any log informational interval 300 (hitcnt=0) 0xd063707c
    access-list inside_access_in line 20 remark CM0000086 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:SSH_internal
    access-list inside_access_in line 21 extended permit tcp 172.31.254.0 255.255.255.0 interface inside eq ssh log informational interval 300 (hitcnt=0) 0x4951b794
    access-list inside_access_in line 22 remark CM0000011 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:PortRange
    access-list inside_access_in line 23 extended permit object TCPPortRange 172.31.254.0 255.255.255.0 host 192.168.20.91 log informational interval 300 (hitcnt=0) 0x441e6d68
      access-list inside_access_in line 23 extended permit tcp 172.31.254.0 255.255.255.0 host 192.168.20.91 range ftp smtp log informational interval 300 (hitcnt=0) 0x441e6d68
    access-list inside_access_in line 24 remark CM0000012 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:FTP
    access-list inside_access_in line 25 extended permit tcp object inside_range range 1024 45000 host 192.168.20.91 eq ftp log informational interval 300 0xe848acd5
      access-list inside_access_in line 25 extended permit tcp range 12.89.235.2 12.89.235.5 range 1024 45000 host 192.168.20.91 eq ftp log informational interval 300 (hitcnt=0) 0xe848acd5
    access-list inside_access_in line 26 extended permit ip 192.168.20.0 255.255.255.0 any log informational interval 300 (hitcnt=0) 0xb6c1be37
    access-list inside_access_in line 27 remark CM0000014 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:DropIP
    access-list inside_access_in line 28 extended permit ip object windowsusageVM any log informational interval 300 (hitcnt=0) 0x22170368
      access-list inside_access_in line 28 extended permit ip host 172.31.254.250 any log informational interval 300 (hitcnt=0) 0x22170368
    access-list inside_access_in line 29 extended permit ip any object testCSM-object (hitcnt=0) 0xa3fcb334
      access-list inside_access_in line 29 extended permit ip any host 255.255.255.255 (hitcnt=0) 0xa3fcb334
    access-list inside_access_in line 30 extended permit ip 172.31.254.0 255.255.255.0 any log informational interval 300 (hitcnt=0) 0xe361b6ed
    access-list inside_access_in line 31 remark CM0000065 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:IP
    access-list inside_access_in line 32 extended permit ip host 172.31.254.2 any log informational interval 300 (hitcnt=0) 0xed7670e1
    access-list inside_access_in line 33 remark CM0000658 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security
    access-list inside_access_in line 34 extended permit tcp host 192.168.20.95 any eq www log informational interval 300 (hitcnt=0) 0x8d07d70b
    There is a comment in the running config: (line 26)
    access-list inside_access_in remark CM0000088 EXP:1/16/2014 OWN:IT_Security BZU:Network_Security JST:PortRange
    This comment is missing in "show access-list". So in the access list, for all the lines after this comment, the line number is no longer correct. This causes problem when we try to use line number to insert a new rule.
    Has anybody seen this problem before? Is this a known problem? I am glad to provide more information if needed.
    Thanks in advance.
    show version:
    Cisco Adaptive Security Appliance Software Version 8.4(4)1
    Device Manager Version 7.1(3)
    Compiled on Thu 14-Jun-12 11:20 by builders
    System image file is "disk0:/asa844-1-k8.bin"
    Config file at boot was "startup-config"
    fmciscoasa up 1 hour 56 mins
    Hardware:   ASA5505, 512 MB RAM, CPU Geode 500 MHz
    Internal ATA Compact Flash, 128MB
    BIOS Flash M50FW016 @ 0xfff00000, 2048KB
    Encryption hardware device : Cisco ASA-5505 on-board accelerator (revision 0x0)
                                 Boot microcode   : CN1000-MC-BOOT-2.00
                                 SSL/IKE microcode: CNLite-MC-SSLm-PLUS-2.03
                                 IPSec microcode  : CNlite-MC-IPSECm-MAIN-2.06
                                 Number of accelerators: 1

    Could be related to the following bug:
    CSCtq12090: ACL remark line is missing when range object is configured in ACL
    Fixed in 8.4(6), so update to a newer version and observe it again.
    Don't stop after you've improved your network! Improve the world by lending money to the working poor:
    http://www.kiva.org/invitedby/karsteni

  • Possible bug related to firefox mime list

    When I was using the gnome3->system settings->system info->default applications I notice several occurrence of firefox. So I browsed my .local/share/applications/ folder to find that sth like:
    userapp-Firefox-NHQB1V.desktop
    userapp-Firefox-Y2ZC1V.desktop
    Those .desktop file actually reflects different version of firefox:
    userapp-Firefox-Y2ZC1V.desktop -> Exec=/usr/lib/firefox-6.0.2/firefox %u
    userapp-Firefox-NHQB1V.desktop-> Exec=/usr/lib/firefox-6.0.1/firefox %u
    Thus I guess whenever I receive a firefox update, gnome is going to create a new firefox phantom desktop file, which is really annoying. Why the damn icon in the application list is not pointed to /usr/bin/firefox instead?

    wonder wrote:those are created by firefox when you answer positive when the browser asks to set it up as default. I personally answer NO and disable that feature and let gnome handle it.
    I was wondering if this should be addressed to gnome or to firefox...After firefox being updated those orphaned .desktop file just remains there and inside the mimeapp.list.

  • Relations between data size and bandwidth

    Hi all,
    We have a engagement with our application in MI25 SP18, (like all app´s, I suppose). About the best relation of amount data transmited and the bandwidth to use.
    Every body knows that the most faster bandwith is the better, but is interesting know this relations.
    I would like to thank for this exceptional forum.
    Thanx to all.
    SCZ
    Message was edited by: Satur Checa

    If you are saying your records fetched by cursor fetch are then to be processed such that there are multiple records to go to BW for each fetched ones, that is doable.
    Fetch your records into a local internal table instead, do the processing and pass the resultant records to the tab that goes back to BW. You only need to make an adjustment to package_size that you specify to the cursor fetch statement. Instead of i_maxsize, pass a value which is divided by the multiplication factor (eg if you create 5 records out of 1 fetched rec, pass the size as a value = i_maxsize/5). If this is not fixed, give an approx so your final no of records are roughly close to the i_maxsize.

  • Possible bug in 3.4.9 and maybe 3.5.3?

    I was going through the logs after a graphics (xorg/radeon/ttm) -this happened today 19/8- related kernel panic and i discovered this from yesterday:
    Aug 18 21:49:07 mainland kernel: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:3406]
    Aug 18 21:49:07 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:07 mainland kernel: CPU 2
    Aug 18 21:49:07 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:07 mainland kernel:
    Aug 18 21:49:07 mainland kernel: Pid: 3406, comm: kworker/2:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
    Aug 18 21:49:07 mainland kernel: RIP: 0010:[<ffffffff8146ad75>] [<ffffffff8146ad75>] _raw_spin_lock+0x35/0x40
    Aug 18 21:49:07 mainland kernel: RSP: 0018:ffff88025ca7bc00 EFLAGS: 00000297
    Aug 18 21:49:07 mainland kernel: RAX: 0000000000000069 RBX: ffff88031ec8e940 RCX: ffff8801584c0580
    Aug 18 21:49:07 mainland kernel: RDX: 000000000000006a RSI: 0000000000000008 RDI: ffffffff81a806fc
    Aug 18 21:49:07 mainland kernel: RBP: ffff88025ca7bc00 R08: ffffffff81618d40 R09: 0000000000000000
    Aug 18 21:49:07 mainland kernel: R10: ffff8802f3ebcf10 R11: 0000000000000000 R12: ffff88025ca7bbd0
    Aug 18 21:49:07 mainland kernel: R13: 0000000000000000 R14: 0200000000000000 R15: 0000000000000000
    Aug 18 21:49:07 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
    Aug 18 21:49:07 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    Aug 18 21:49:07 mainland kernel: CR2: 00007f850dc67000 CR3: 000000000380b000 CR4: 00000000001407e0
    Aug 18 21:49:07 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Aug 18 21:49:07 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Aug 18 21:49:07 mainland kernel: Process kworker/2:2 (pid: 3406, threadinfo ffff88025ca7a000, task ffff8802c7cfdf40)
    Aug 18 21:49:07 mainland kernel: Stack:
    Aug 18 21:49:07 mainland kernel: ffff88025ca7bc10 ffffffff811b8955 ffff88025ca7bcf0 ffffffff811badd2
    Aug 18 21:49:07 mainland kernel: ffff88025ca7bc50 ffffffff81159f6d ffff88025ca7bc60 ffff88029b923210
    Aug 18 21:49:07 mainland kernel: ffff88025ca7bfd8 ffff88025ca7bfd8 ffff88025ca7bc70 ffffffff8118492b
    Aug 18 21:49:07 mainland kernel: Call Trace:
    Aug 18 21:49:07 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:07 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
    Aug 18 21:49:07 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
    Aug 18 21:49:07 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
    Aug 18 21:49:07 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
    Aug 18 21:49:07 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
    Aug 18 21:49:07 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
    Aug 18 21:49:07 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
    Aug 18 21:49:07 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
    Aug 18 21:49:07 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
    Aug 18 21:49:07 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
    Aug 18 21:49:07 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
    Aug 18 21:49:07 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
    Aug 18 21:49:07 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
    Aug 18 21:49:07 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
    Aug 18 21:49:07 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
    Aug 18 21:49:07 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
    Aug 18 21:49:07 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
    Aug 18 21:49:07 mainland kernel: Code: 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00 00 f3 90
    Aug 18 21:49:07 mainland kernel: Call Trace:
    Aug 18 21:49:07 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:07 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
    Aug 18 21:49:07 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
    Aug 18 21:49:07 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
    Aug 18 21:49:07 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
    Aug 18 21:49:07 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
    Aug 18 21:49:07 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
    Aug 18 21:49:07 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
    Aug 18 21:49:07 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
    Aug 18 21:49:07 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
    Aug 18 21:49:07 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
    Aug 18 21:49:07 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
    Aug 18 21:49:07 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
    Aug 18 21:49:07 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
    Aug 18 21:49:07 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
    Aug 18 21:49:07 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
    Aug 18 21:49:07 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
    Aug 18 21:49:07 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
    Aug 18 21:49:08 mainland kernel: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:2:3797]
    Aug 18 21:49:08 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:08 mainland kernel: CPU 3
    Aug 18 21:49:08 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:08 mainland kernel:
    Aug 18 21:49:08 mainland kernel: Pid: 3797, comm: kworker/3:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
    Aug 18 21:49:08 mainland kernel: RIP: 0010:[<ffffffff811badeb>] [<ffffffff811badeb>] locks_remove_flock+0xdb/0x130
    Aug 18 21:49:08 mainland kernel: RSP: 0018:ffff880259133c20 EFLAGS: 00000286
    Aug 18 21:49:08 mainland kernel: RAX: ffff88029b923830 RBX: ffff880259133fd8 RCX: ffff8801584c0550
    Aug 18 21:49:08 mainland kernel: RDX: 0000000000000069 RSI: 0000000000000008 RDI: ffffffff81a806fc
    Aug 18 21:49:08 mainland kernel: RBP: ffff880259133cf0 R08: ffffffff81618d40 R09: 0000000000000000
    Aug 18 21:49:08 mainland kernel: R10: ffff88025f179610 R11: 0000000000000000 R12: ffff880259133bf0
    Aug 18 21:49:08 mainland kernel: R13: 0000000100000002 R14: 0000000000000000 R15: 0000000000000297
    Aug 18 21:49:08 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ecc0000(0000) knlGS:0000000000000000
    Aug 18 21:49:08 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    Aug 18 21:49:08 mainland kernel: CR2: 00007f8507a34000 CR3: 000000000380b000 CR4: 00000000001407e0
    Aug 18 21:49:08 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Aug 18 21:49:08 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Aug 18 21:49:08 mainland kernel: Process kworker/3:2 (pid: 3797, threadinfo ffff880259132000, task ffff88025ae727b0)
    Aug 18 21:49:08 mainland kernel: Stack:
    Aug 18 21:49:08 mainland kernel: ffff880259133c50 ffffffff81159f6d ffff880259133c60 ffff88029ba652d0
    Aug 18 21:49:08 mainland kernel: ffff880259133fd8 ffff880259133fd8 ffff880259133c70 ffffffff8118492b
    Aug 18 21:49:08 mainland kernel: ffff88029ba65240 000000018040002b 0000000059133c90 0000000000000000
    Aug 18 21:49:08 mainland kernel: Call Trace:
    Aug 18 21:49:08 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
    Aug 18 21:49:08 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
    Aug 18 21:49:08 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
    Aug 18 21:49:08 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
    Aug 18 21:49:08 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
    Aug 18 21:49:08 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
    Aug 18 21:49:08 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
    Aug 18 21:49:08 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
    Aug 18 21:49:08 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
    Aug 18 21:49:08 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
    Aug 18 21:49:08 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
    Aug 18 21:49:08 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
    Aug 18 21:49:08 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
    Aug 18 21:49:08 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
    Aug 18 21:49:08 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
    Aug 18 21:49:08 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
    Aug 18 21:49:08 mainland kernel: Code: 85 c0 74 09 48 8d bd 30 ff ff ff ff d0 e8 6e db ff ff 48 81 c3 48 01 00 00 eb 08 0f 1f 44 00 00 48 89 c3 48 8b 03 48 85
    Aug 18 21:49:08 mainland kernel: Call Trace:
    Aug 18 21:49:08 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
    Aug 18 21:49:08 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
    Aug 18 21:49:08 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
    Aug 18 21:49:08 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
    Aug 18 21:49:08 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
    Aug 18 21:49:08 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
    Aug 18 21:49:08 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
    Aug 18 21:49:08 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
    Aug 18 21:49:08 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
    Aug 18 21:49:08 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
    Aug 18 21:49:08 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
    Aug 18 21:49:08 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
    Aug 18 21:49:08 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
    Aug 18 21:49:08 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
    Aug 18 21:49:08 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
    Aug 18 21:49:08 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
    Aug 18 21:49:27 mainland kernel: BUG: soft lockup - CPU#0 stuck for 22s! [firefox:3820]
    Aug 18 21:49:27 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:27 mainland kernel: CPU 0
    Aug 18 21:49:27 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:27 mainland kernel:
    Aug 18 21:49:27 mainland kernel: Pid: 3820, comm: firefox Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
    Aug 18 21:49:27 mainland kernel: RIP: 0010:[<ffffffff8146ad72>] [<ffffffff8146ad72>] _raw_spin_lock+0x32/0x40
    Aug 18 21:49:27 mainland kernel: RSP: 0018:ffff880157001dd8 EFLAGS: 00000293
    Aug 18 21:49:27 mainland kernel: RAX: 0000000000000069 RBX: 0000000000000001 RCX: 0000000000000000
    Aug 18 21:49:27 mainland kernel: RDX: 000000000000006b RSI: ffffffff816f15a2 RDI: ffffffff81a806fc
    Aug 18 21:49:27 mainland kernel: RBP: ffff880157001dd8 R08: 0000000000016490 R09: ffff8802fd7c8900
    Aug 18 21:49:27 mainland kernel: R10: 0000000000000002 R11: 0000000000000293 R12: 00000000ffffffff
    Aug 18 21:49:27 mainland kernel: R13: 0000000000000000 R14: ffff88030b76c600 R15: 0000000000000000
    Aug 18 21:49:27 mainland kernel: FS: 00007fe462bff700(0000) GS:ffff88031ec00000(0000) knlGS:0000000000000000
    Aug 18 21:49:27 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Aug 18 21:49:27 mainland kernel: CR2: 00007f850dd47000 CR3: 000000025aa34000 CR4: 00000000001407f0
    Aug 18 21:49:27 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Aug 18 21:49:27 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Aug 18 21:49:27 mainland kernel: Process firefox (pid: 3820, threadinfo ffff880157000000, task ffff8802c7cfc770)
    Aug 18 21:49:27 mainland kernel: Stack:
    Aug 18 21:49:27 mainland kernel: ffff880157001de8 ffffffff811b8955 ffff880157001e48 ffffffff811b9465
    Aug 18 21:49:27 mainland kernel: ffff8802c7cfcc00 ffffffff81159e4f ffff8802fd7c8900 0000000000000000
    Aug 18 21:49:27 mainland kernel: ffff880157001e48 ffff8802fd7c8840 0000000000000000 ffff8802c7cfc770
    Aug 18 21:49:27 mainland kernel: Call Trace:
    Aug 18 21:49:27 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:27 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
    Aug 18 21:49:27 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
    Aug 18 21:49:27 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
    Aug 18 21:49:27 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
    Aug 18 21:49:27 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
    Aug 18 21:49:27 mainland kernel: [<ffffffff810aafa2>] ? sys_futex+0x102/0x190
    Aug 18 21:49:27 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
    Aug 18 21:49:27 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
    Aug 18 21:49:27 mainland kernel: Code: 00 00 65 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00
    Aug 18 21:49:27 mainland kernel: Call Trace:
    Aug 18 21:49:27 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:27 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
    Aug 18 21:49:27 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
    Aug 18 21:49:27 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
    Aug 18 21:49:27 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
    Aug 18 21:49:27 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
    Aug 18 21:49:27 mainland kernel: [<ffffffff810aafa2>] ? sys_futex+0x102/0x190
    Aug 18 21:49:27 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
    Aug 18 21:49:27 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
    Aug 18 21:49:35 mainland kernel: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:3406]
    Aug 18 21:49:35 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:35 mainland kernel: CPU 2
    Aug 18 21:49:35 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:35 mainland kernel:
    Aug 18 21:49:35 mainland kernel: Pid: 3406, comm: kworker/2:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
    Aug 18 21:49:35 mainland kernel: RIP: 0010:[<ffffffff8146ad75>] [<ffffffff8146ad75>] _raw_spin_lock+0x35/0x40
    Aug 18 21:49:35 mainland kernel: RSP: 0018:ffff88025ca7bc00 EFLAGS: 00000297
    Aug 18 21:49:35 mainland kernel: RAX: 0000000000000069 RBX: ffff88031ec8e940 RCX: ffff8801584c0580
    Aug 18 21:49:35 mainland kernel: RDX: 000000000000006a RSI: 0000000000000008 RDI: ffffffff81a806fc
    Aug 18 21:49:35 mainland kernel: RBP: ffff88025ca7bc00 R08: ffffffff81618d40 R09: 0000000000000000
    Aug 18 21:49:35 mainland kernel: R10: ffff8802f3ebcf10 R11: 0000000000000000 R12: ffff88025ca7bbd0
    Aug 18 21:49:35 mainland kernel: R13: 0000000000000000 R14: 0200000000000000 R15: 0000000000000000
    Aug 18 21:49:35 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
    Aug 18 21:49:35 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    Aug 18 21:49:35 mainland kernel: CR2: 00007f850dc67000 CR3: 000000000380b000 CR4: 00000000001407e0
    Aug 18 21:49:35 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Aug 18 21:49:35 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Aug 18 21:49:35 mainland kernel: Process kworker/2:2 (pid: 3406, threadinfo ffff88025ca7a000, task ffff8802c7cfdf40)
    Aug 18 21:49:35 mainland kernel: Stack:
    Aug 18 21:49:35 mainland kernel: ffff88025ca7bc10 ffffffff811b8955 ffff88025ca7bcf0 ffffffff811badd2
    Aug 18 21:49:35 mainland kernel: ffff88025ca7bc50 ffffffff81159f6d ffff88025ca7bc60 ffff88029b923210
    Aug 18 21:49:35 mainland kernel: ffff88025ca7bfd8 ffff88025ca7bfd8 ffff88025ca7bc70 ffffffff8118492b
    Aug 18 21:49:35 mainland kernel: Call Trace:
    Aug 18 21:49:35 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:35 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
    Aug 18 21:49:35 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
    Aug 18 21:49:35 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
    Aug 18 21:49:35 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
    Aug 18 21:49:35 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
    Aug 18 21:49:35 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
    Aug 18 21:49:35 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
    Aug 18 21:49:35 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
    Aug 18 21:49:35 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
    Aug 18 21:49:35 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
    Aug 18 21:49:35 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
    Aug 18 21:49:35 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
    Aug 18 21:49:35 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
    Aug 18 21:49:35 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
    Aug 18 21:49:35 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
    Aug 18 21:49:35 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
    Aug 18 21:49:35 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
    Aug 18 21:49:35 mainland kernel: Code: 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00 00 f3 90
    Aug 18 21:49:35 mainland kernel: Call Trace:
    Aug 18 21:49:35 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:35 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
    Aug 18 21:49:35 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
    Aug 18 21:49:35 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
    Aug 18 21:49:35 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
    Aug 18 21:49:35 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
    Aug 18 21:49:35 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
    Aug 18 21:49:35 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
    Aug 18 21:49:35 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
    Aug 18 21:49:35 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
    Aug 18 21:49:35 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
    Aug 18 21:49:35 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
    Aug 18 21:49:35 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
    Aug 18 21:49:35 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
    Aug 18 21:49:35 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
    Aug 18 21:49:35 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
    Aug 18 21:49:35 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
    Aug 18 21:49:35 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
    Aug 18 21:49:36 mainland kernel: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:2:3797]
    Aug 18 21:49:36 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:36 mainland kernel: CPU 3
    Aug 18 21:49:36 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:36 mainland kernel:
    Aug 18 21:49:36 mainland kernel: Pid: 3797, comm: kworker/3:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
    Aug 18 21:49:36 mainland kernel: RIP: 0010:[<ffffffff811badeb>] [<ffffffff811badeb>] locks_remove_flock+0xdb/0x130
    Aug 18 21:49:36 mainland kernel: RSP: 0018:ffff880259133c20 EFLAGS: 00000282
    Aug 18 21:49:36 mainland kernel: RAX: ffff8801584c0698 RBX: ffff880259133fd8 RCX: ffff8801584c0550
    Aug 18 21:49:36 mainland kernel: RDX: 0000000000000069 RSI: 0000000000000008 RDI: ffffffff81a806fc
    Aug 18 21:49:36 mainland kernel: RBP: ffff880259133cf0 R08: ffffffff81618d40 R09: 0000000000000000
    Aug 18 21:49:36 mainland kernel: R10: ffff88025f179610 R11: 0000000000000000 R12: ffff880259133bf0
    Aug 18 21:49:36 mainland kernel: R13: 0000000100000002 R14: 0000000000000000 R15: 0000000000000297
    Aug 18 21:49:36 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ecc0000(0000) knlGS:0000000000000000
    Aug 18 21:49:36 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    Aug 18 21:49:36 mainland kernel: CR2: 00007f8507a34000 CR3: 000000000380b000 CR4: 00000000001407e0
    Aug 18 21:49:36 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Aug 18 21:49:36 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Aug 18 21:49:36 mainland kernel: Process kworker/3:2 (pid: 3797, threadinfo ffff880259132000, task ffff88025ae727b0)
    Aug 18 21:49:36 mainland kernel: Stack:
    Aug 18 21:49:36 mainland kernel: ffff880259133c50 ffffffff81159f6d ffff880259133c60 ffff88029ba652d0
    Aug 18 21:49:36 mainland kernel: ffff880259133fd8 ffff880259133fd8 ffff880259133c70 ffffffff8118492b
    Aug 18 21:49:36 mainland kernel: ffff88029ba65240 000000018040002b 0000000059133c90 0000000000000000
    Aug 18 21:49:36 mainland kernel: Call Trace:
    Aug 18 21:49:36 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
    Aug 18 21:49:36 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
    Aug 18 21:49:36 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
    Aug 18 21:49:36 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
    Aug 18 21:49:36 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
    Aug 18 21:49:36 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
    Aug 18 21:49:36 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
    Aug 18 21:49:36 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
    Aug 18 21:49:36 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
    Aug 18 21:49:36 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
    Aug 18 21:49:36 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
    Aug 18 21:49:36 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
    Aug 18 21:49:36 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
    Aug 18 21:49:36 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
    Aug 18 21:49:36 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
    Aug 18 21:49:36 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
    Aug 18 21:49:36 mainland kernel: Code: 85 c0 74 09 48 8d bd 30 ff ff ff ff d0 e8 6e db ff ff 48 81 c3 48 01 00 00 eb 08 0f 1f 44 00 00 48 89 c3 48 8b 03 48 85
    Aug 18 21:49:36 mainland kernel: Call Trace:
    Aug 18 21:49:36 mainland kernel: [<ffffffff81159f6d>] ? kmem_cache_free+0x10d/0x120
    Aug 18 21:49:36 mainland kernel: [<ffffffff8118492b>] ? __d_free+0x4b/0x70
    Aug 18 21:49:36 mainland kernel: [<ffffffff81170764>] fput+0xb4/0x260
    Aug 18 21:49:36 mainland kernel: [<ffffffffa0010e07>] drm_gem_object_release+0x17/0x20 [drm]
    Aug 18 21:49:36 mainland kernel: [<ffffffffa00b3e1d>] radeon_ttm_bo_destroy+0xad/0xd0 [radeon]
    Aug 18 21:49:36 mainland kernel: [<ffffffffa0057b6e>] ttm_bo_release_list+0xae/0xf0 [ttm]
    Aug 18 21:49:36 mainland kernel: [<ffffffffa005881d>] ttm_bo_delayed_delete+0x10d/0x1c0 [ttm]
    Aug 18 21:49:36 mainland kernel: [<ffffffffa00588ef>] ttm_bo_delayed_workqueue+0x1f/0x40 [ttm]
    Aug 18 21:49:36 mainland kernel: [<ffffffff8106d4ba>] process_one_work+0x12a/0x440
    Aug 18 21:49:36 mainland kernel: [<ffffffffa00588d0>] ? ttm_bo_delayed_delete+0x1c0/0x1c0 [ttm]
    Aug 18 21:49:36 mainland kernel: [<ffffffff8106dd1e>] worker_thread+0x12e/0x2d0
    Aug 18 21:49:36 mainland kernel: [<ffffffff8106dbf0>] ? manage_workers.isra.26+0x1f0/0x1f0
    Aug 18 21:49:36 mainland kernel: [<ffffffff810731c3>] kthread+0x93/0xa0
    Aug 18 21:49:36 mainland kernel: [<ffffffff8146d2a4>] kernel_thread_helper+0x4/0x10
    Aug 18 21:49:36 mainland kernel: [<ffffffff81073130>] ? kthread_freezable_should_stop+0x70/0x70
    Aug 18 21:49:36 mainland kernel: [<ffffffff8146d2a0>] ? gs_change+0x13/0x13
    Aug 18 21:49:36 mainland kernel: BUG: soft lockup - CPU#6 stuck for 22s! [firefox:3805]
    Aug 18 21:49:36 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:36 mainland kernel: CPU 6
    Aug 18 21:49:36 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:36 mainland kernel:
    Aug 18 21:49:36 mainland kernel: Pid: 3805, comm: firefox Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
    Aug 18 21:49:36 mainland kernel: RIP: 0010:[<ffffffff8146ad75>] [<ffffffff8146ad75>] _raw_spin_lock+0x35/0x40
    Aug 18 21:49:36 mainland kernel: RSP: 0018:ffff8802f433fdd8 EFLAGS: 00000293
    Aug 18 21:49:36 mainland kernel: RAX: 0000000000000069 RBX: 0000000000000000 RCX: 0000000000000000
    Aug 18 21:49:36 mainland kernel: RDX: 000000000000006c RSI: ffffffff816f15a2 RDI: ffffffff81a806fc
    Aug 18 21:49:36 mainland kernel: RBP: ffff8802f433fdd8 R08: 0000000000016490 R09: ffff8802bde4ef00
    Aug 18 21:49:36 mainland kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
    Aug 18 21:49:36 mainland kernel: R13: ffff8802f433e000 R14: ffffffff81132ceb R15: ffff8802f433fdf8
    Aug 18 21:49:36 mainland kernel: FS: 00007fe47e1a7740(0000) GS:ffff88031ed80000(0000) knlGS:0000000000000000
    Aug 18 21:49:36 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Aug 18 21:49:36 mainland kernel: CR2: 00007fe4583c1000 CR3: 000000025aa34000 CR4: 00000000001407e0
    Aug 18 21:49:36 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Aug 18 21:49:36 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Aug 18 21:49:36 mainland kernel: Process firefox (pid: 3805, threadinfo ffff8802f433e000, task ffff8802c7cf8000)
    Aug 18 21:49:36 mainland kernel: Stack:
    Aug 18 21:49:36 mainland kernel: ffff8802f433fde8 ffffffff811b8955 ffff8802f433fe48 ffffffff811b9465
    Aug 18 21:49:36 mainland kernel: ffff8802f433fe38 ffffffff81159e4f ffff8802bde4ef00 00007fe4583c1000
    Aug 18 21:49:36 mainland kernel: 0000000000000029 ffff8802bde4ec00 0000000000000000 ffff8802c7cf8000
    Aug 18 21:49:36 mainland kernel: Call Trace:
    Aug 18 21:49:36 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:36 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
    Aug 18 21:49:36 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
    Aug 18 21:49:36 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
    Aug 18 21:49:36 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
    Aug 18 21:49:36 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
    Aug 18 21:49:36 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
    Aug 18 21:49:36 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
    Aug 18 21:49:36 mainland kernel: Code: 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00 00 f3 90
    Aug 18 21:49:36 mainland kernel: Call Trace:
    Aug 18 21:49:36 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:36 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
    Aug 18 21:49:36 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
    Aug 18 21:49:36 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
    Aug 18 21:49:36 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
    Aug 18 21:49:36 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
    Aug 18 21:49:36 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
    Aug 18 21:49:36 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
    Aug 18 21:49:55 mainland kernel: BUG: soft lockup - CPU#0 stuck for 22s! [firefox:3820]
    Aug 18 21:49:55 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:55 mainland kernel: CPU 0
    Aug 18 21:49:55 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:49:55 mainland kernel:
    Aug 18 21:49:55 mainland kernel: Pid: 3820, comm: firefox Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
    Aug 18 21:49:55 mainland kernel: RIP: 0010:[<ffffffff8146ad72>] [<ffffffff8146ad72>] _raw_spin_lock+0x32/0x40
    Aug 18 21:49:55 mainland kernel: RSP: 0018:ffff880157001dd8 EFLAGS: 00000293
    Aug 18 21:49:55 mainland kernel: RAX: 0000000000000069 RBX: 0000000000000001 RCX: 0000000000000000
    Aug 18 21:49:55 mainland kernel: RDX: 000000000000006b RSI: ffffffff816f15a2 RDI: ffffffff81a806fc
    Aug 18 21:49:55 mainland kernel: RBP: ffff880157001dd8 R08: 0000000000016490 R09: ffff8802fd7c8900
    Aug 18 21:49:55 mainland kernel: R10: 0000000000000002 R11: 0000000000000293 R12: 00000000ffffffff
    Aug 18 21:49:55 mainland kernel: R13: 0000000000000000 R14: ffff88030b76c600 R15: 0000000000000000
    Aug 18 21:49:55 mainland kernel: FS: 00007fe462bff700(0000) GS:ffff88031ec00000(0000) knlGS:0000000000000000
    Aug 18 21:49:55 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Aug 18 21:49:55 mainland kernel: CR2: 00007f850dd47000 CR3: 000000025aa34000 CR4: 00000000001407f0
    Aug 18 21:49:55 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Aug 18 21:49:55 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Aug 18 21:49:55 mainland kernel: Process firefox (pid: 3820, threadinfo ffff880157000000, task ffff8802c7cfc770)
    Aug 18 21:49:55 mainland kernel: Stack:
    Aug 18 21:49:55 mainland kernel: ffff880157001de8 ffffffff811b8955 ffff880157001e48 ffffffff811b9465
    Aug 18 21:49:55 mainland kernel: ffff8802c7cfcc00 ffffffff81159e4f ffff8802fd7c8900 0000000000000000
    Aug 18 21:49:55 mainland kernel: ffff880157001e48 ffff8802fd7c8840 0000000000000000 ffff8802c7cfc770
    Aug 18 21:49:55 mainland kernel: Call Trace:
    Aug 18 21:49:55 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:55 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
    Aug 18 21:49:55 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
    Aug 18 21:49:55 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
    Aug 18 21:49:55 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
    Aug 18 21:49:55 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
    Aug 18 21:49:55 mainland kernel: [<ffffffff810aafa2>] ? sys_futex+0x102/0x190
    Aug 18 21:49:55 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
    Aug 18 21:49:55 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
    Aug 18 21:49:55 mainland kernel: Code: 00 00 65 48 8b 04 25 f0 c6 00 00 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 74 0f 66 0f 1f 44 00
    Aug 18 21:49:55 mainland kernel: Call Trace:
    Aug 18 21:49:55 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:49:55 mainland kernel: [<ffffffff811b9465>] __posix_lock_file+0x45/0x490
    Aug 18 21:49:55 mainland kernel: [<ffffffff81159e4f>] ? kmem_cache_alloc+0x13f/0x150
    Aug 18 21:49:55 mainland kernel: [<ffffffff811b98c6>] posix_lock_file+0x16/0x20
    Aug 18 21:49:55 mainland kernel: [<ffffffff811b9905>] vfs_lock_file+0x35/0x40
    Aug 18 21:49:55 mainland kernel: [<ffffffff811bab47>] fcntl_setlk+0x147/0x310
    Aug 18 21:49:55 mainland kernel: [<ffffffff810aafa2>] ? sys_futex+0x102/0x190
    Aug 18 21:49:55 mainland kernel: [<ffffffff8117fba5>] sys_fcntl+0x135/0x560
    Aug 18 21:49:55 mainland kernel: [<ffffffff8146bfa9>] system_call_fastpath+0x16/0x1b
    Aug 18 21:50:03 mainland kernel: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:3406]
    Aug 18 21:50:03 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:50:03 mainland kernel: CPU 2
    Aug 18 21:50:03 mainland kernel: Modules linked in: fuse w83627ehf hwmon_vid nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek microcode aesni_intel
    Aug 18 21:50:03 mainland kernel:
    Aug 18 21:50:03 mainland kernel: Pid: 3406, comm: kworker/2:2 Tainted: G C 3.4.9-1-ARCH #1 /DZ77BH-55K
    Aug 18 21:50:03 mainland kernel: RIP: 0010:[<ffffffff8146ad72>] [<ffffffff8146ad72>] _raw_spin_lock+0x32/0x40
    Aug 18 21:50:03 mainland kernel: RSP: 0018:ffff88025ca7bc00 EFLAGS: 00000297
    Aug 18 21:50:03 mainland kernel: RAX: 0000000000000069 RBX: ffff88031ec8e940 RCX: ffff8801584c0580
    Aug 18 21:50:03 mainland kernel: RDX: 000000000000006a RSI: 0000000000000008 RDI: ffffffff81a806fc
    Aug 18 21:50:03 mainland kernel: RBP: ffff88025ca7bc00 R08: ffffffff81618d40 R09: 0000000000000000
    Aug 18 21:50:03 mainland kernel: R10: ffff8802f3ebcf10 R11: 0000000000000000 R12: ffff88025ca7bbd0
    Aug 18 21:50:03 mainland kernel: R13: 0000000000000000 R14: 0200000000000000 R15: 0000000000000000
    Aug 18 21:50:03 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
    Aug 18 21:50:03 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    Aug 18 21:50:03 mainland kernel: CR2: 00007f850dc67000 CR3: 000000000380b000 CR4: 00000000001407e0
    Aug 18 21:50:03 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Aug 18 21:50:03 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Aug 18 21:50:03 mainland kernel: Process kworker/2:2 (pid: 3406, threadinfo ffff88025ca7a000, task ffff8802c7cfdf40)
    Aug 18 21:50:03 mainland kernel: Stack:
    Aug 18 21:50:03 mainland kernel: ffff88025ca7bc10 ffffffff811b8955 ffff88025ca7bcf0 ffffffff811badd2
    Aug 18 21:50:03 mainland kernel: ffff88025ca7bc50 ffffffff81159f6d ffff88025ca7bc60 ffff88029b923210
    Aug 18 21:50:03 mainland kernel: ffff88025ca7bfd8 ffff88025ca7bfd8 ffff88025ca7bc70 ffffffff8118492b
    Aug 18 21:50:03 mainland kernel: Call Trace:
    Aug 18 21:50:03 mainland kernel: [<ffffffff811b8955>] lock_flocks+0x15/0x20
    Aug 18 21:50:03 mainland kernel: [<ffffffff811badd2>] locks_remove_flock+0xc2/0x130
    Any ideas and anything i can do?
    Last edited by 89c51 (2012-08-31 20:26:13)

    Sorry for bumping but i got this beauty some minutes ago.
    Sep 20 20:13:00 mainland dbus[378]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.0" (uid=0 pid=376 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" me
    Sep 20 22:35:53 mainland kernel: general protection fault: 0000 [#1] PREEMPT SMP
    Sep 20 22:35:53 mainland kernel: CPU 2
    Sep 20 22:35:53 mainland kernel: Modules linked in:
    Sep 20 22:35:53 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
    Sep 20 22:35:53 mainland kernel:
    Sep 20 22:35:53 mainland kernel: Pid: 402, comm: Xorg Not tainted 3.5.4-1-ARCH #1 /DZ77BH-55K
    Sep 20 22:35:53 mainland kernel: RIP: 0010:[<ffffffff811643fb>] [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:35:53 mainland kernel: RSP: 0018:ffff8803009898c8 EFLAGS: 00010286
    Sep 20 22:35:53 mainland kernel: RAX: 0000000000000000 RBX: 0000000000000002 RCX: 00000000465a5002
    Sep 20 22:35:53 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000000d0 RDI: ffffffffa0064871
    Sep 20 22:35:53 mainland kernel: RBP: ffff880300989908 R08: 0000000000016710 R09: 00000000001c0217
    Sep 20 22:35:53 mainland kernel: R10: 0000000000000002 R11: ffffffffa00649a8 R12: 00000000000000d0
    Sep 20 22:35:53 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: ffff88030d1143c0
    Sep 20 22:35:53 mainland kernel: FS: 00007f7f13315880(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
    Sep 20 22:35:53 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep 20 22:35:53 mainland kernel: CR2: 00007f7f0b5d1000 CR3: 000000030092a000 CR4: 00000000001407e0
    Sep 20 22:35:53 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Sep 20 22:35:53 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Sep 20 22:35:53 mainland kernel: Process Xorg (pid: 402, threadinfo ffff880300988000, task ffff88030a1e1020)
    Sep 20 22:35:53 mainland kernel: Stack:
    Sep 20 22:35:53 mainland kernel: 00000000000200d0 0000000000000028 ffff880300989908 0000000000000002
    Sep 20 22:35:53 mainland kernel: 0000000000000002 ffff88016733c4c0 ffff88025307ca00 ffff88030d1143c0
    Sep 20 22:35:53 mainland kernel: ffff8803009899f8 ffffffffa0064871 ffff880300989938 ffffffff8114b9db
    Sep 20 22:35:53 mainland kernel: Call Trace:
    Sep 20 22:35:53 mainland kernel: [<ffffffffa0064871>] ttm_dma_populate+0x551/0x990 [ttm]
    Sep 20 22:35:53 mainland kernel: [<ffffffff8114b9db>] ? insert_vmalloc_vmlist+0x6b/0x80
    Sep 20 22:35:53 mainland kernel: [<ffffffff8114e505>] ? __vmalloc_node+0x35/0x40
    Sep 20 22:35:53 mainland kernel: [<ffffffffa00b68df>] radeon_ttm_tt_populate+0x22f/0x260 [radeon]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa00b699c>] ? radeon_ttm_tt_create+0x8c/0x100 [radeon]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa005b0be>] ttm_tt_bind+0x3e/0x70 [ttm]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa005d387>] ttm_bo_handle_move_mem+0x507/0x590 [ttm]
    Sep 20 22:35:53 mainland kernel: [<ffffffff811926e7>] ? inode_init_always+0x107/0x1d0
    Sep 20 22:35:53 mainland kernel: [<ffffffffa005e392>] ttm_bo_move_buffer+0x142/0x150 [ttm]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa005e43d>] ttm_bo_validate+0x9d/0x120 [ttm]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa005e7cf>] ttm_bo_init+0x30f/0x3e0 [ttm]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa00b75c6>] radeon_bo_create+0x1b6/0x300 [radeon]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa00b7290>] ? radeon_bo_clear_va+0xd0/0xd0 [radeon]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa00c9491>] radeon_gem_object_create+0x61/0x100 [radeon]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa00c989a>] radeon_gem_create_ioctl+0x5a/0xf0 [radeon]
    Sep 20 22:35:53 mainland kernel: [<ffffffff8147b83e>] ? mutex_unlock+0xe/0x10
    Sep 20 22:35:53 mainland kernel: [<ffffffffa00c9b18>] ? radeon_gem_busy_ioctl+0x98/0x110 [radeon]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa00104f3>] drm_ioctl+0x4c3/0x570 [drm]
    Sep 20 22:35:53 mainland kernel: [<ffffffffa00c9840>] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
    Sep 20 22:35:53 mainland kernel: [<ffffffff814815c4>] ? do_page_fault+0x2c4/0x580
    Sep 20 22:35:53 mainland kernel: [<ffffffff811463ed>] ? do_mmap_pgoff+0x24d/0x340
    Sep 20 22:35:53 mainland kernel: [<ffffffff8118aad7>] do_vfs_ioctl+0x97/0x530
    Sep 20 22:35:53 mainland kernel: [<ffffffff8118b009>] sys_ioctl+0x99/0xa0
    Sep 20 22:35:53 mainland kernel: [<ffffffff814853ed>] system_call_fastpath+0x1a/0x1f
    Sep 20 22:35:53 mainland kernel: Code: 48 89 55 c8 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 28 4d 85 ed 0f 84 c7 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 5c 05 00 4c 89 e8 65 49
    Sep 20 22:35:53 mainland kernel: RIP [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:35:53 mainland kernel: RSP <ffff8803009898c8>
    Sep 20 22:35:53 mainland kernel: ---[ end trace 6841e94d0f65e4c5 ]---
    Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#2] PREEMPT SMP
    Sep 20 22:36:11 mainland kernel: CPU 2
    Sep 20 22:36:11 mainland kernel: Modules linked in:
    Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: Pid: 378, comm: dbus-daemon Tainted: G D 3.5.4-1-ARCH #1 /DZ77BH-55K
    Sep 20 22:36:11 mainland avahi-daemon[371]: Disconnected from D-Bus, exiting.
    Sep 20 22:36:11 mainland avahi-daemon[371]: Got SIGTERM, quitting.
    Sep 20 22:36:11 mainland avahi-daemon[371]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
    Sep 20 22:36:11 mainland NetworkManager[364]: <warn> disconnected by the system bus.
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Exiting cleanly.
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Demoting known real-time threads.
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 699 of process 699 (/usr/bin/pulseaudio).
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 598 of process 565 (/usr/bin/pulseaudio).
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 597 of process 565 (/usr/bin/pulseaudio).
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 593 of process 565 (/usr/bin/pulseaudio).
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Successfully demoted thread 565 of process 565 (/usr/bin/pulseaudio).
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Demoted 5 threads.
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Exiting watchdog thread.
    Sep 20 22:36:11 mainland rtkit-daemon[567]: Exiting canary thread.
    Sep 20 22:36:11 mainland avahi-daemon[371]: avahi-daemon 0.6.31 exiting.
    Sep 20 22:36:11 mainland gdm-simple-slave[399]: WARNING: Child process 611 was already dead.
    Sep 20 22:36:11 mainland gdm-simple-slave[399]: WARNING: Unable to kill session worker process
    Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff811643fb>] [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:36:11 mainland NetworkManager[364]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Sep 20 22:36:11 mainland colord[709]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Sep 20 22:36:11 mainland colord-sane[721]: Failed cupsGetDevices
    Sep 20 22:36:11 mainland colord-sane[721]: Failed cupsGetDevices
    Sep 20 22:36:11 mainland colord-sane[721]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Sep 20 22:36:11 mainland accounts-daemon[427]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    Sep 20 22:36:11 mainland systemd[1]: upower.service: main process exited, code=exited, status=1
    Sep 20 22:36:11 mainland console-kit-daemon[430]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting
    Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff88030b555de8 EFLAGS: 00010286
    Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: ffff88030afdf3b0 RCX: 00000000465a5002
    Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000080d0 RDI: ffffffffa022144d
    Sep 20 22:36:11 mainland kernel: RBP: ffff88030b555e28 R08: 0000000000016710 R09: 2222222222222222
    Sep 20 22:36:11 mainland kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000080d0
    Sep 20 22:36:11 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: ffff88030a101d00
    Sep 20 22:36:11 mainland kernel: FS: 00007f8e02dec700(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
    Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep 20 22:36:11 mainland kernel: CR2: 00007f7f0b5d1000 CR3: 000000030c2bf000 CR4: 00000000001407e0
    Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Sep 20 22:36:11 mainland kernel: Process dbus-daemon (pid: 378, threadinfo ffff88030b554000, task ffff88030a1e2850)
    Sep 20 22:36:11 mainland kernel: Stack:
    Sep 20 22:36:11 mainland kernel: ffff88030bc66020 0000000000000030 ffff88030b555e08 ffff88030afdf3b0
    Sep 20 22:36:11 mainland kernel: ffff88030afdf3b0 0000000000000000 ffff88030a06a000 ffff88030a101d00
    Sep 20 22:36:11 mainland kernel: ffff88030b555ed8 ffffffffa022144d ffff88030b555eb8 ffffffff8147b116
    Sep 20 22:36:11 mainland kernel: Call Trace:
    Sep 20 22:36:11 mainland kernel: [<ffffffffa022144d>] ext4_readdir+0x68d/0x7c0 [ext4]
    Sep 20 22:36:11 mainland kernel: [<ffffffff8147b116>] ? __mutex_lock_killable_slowpath+0x266/0x3f0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8118b010>] ? sys_ioctl+0xa0/0xa0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8118b010>] ? sys_ioctl+0xa0/0xa0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8118b010>] ? sys_ioctl+0xa0/0xa0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8118b358>] vfs_readdir+0xb8/0xe0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8118b480>] sys_getdents+0x80/0x100
    Sep 20 22:36:11 mainland kernel: [<ffffffff814853ed>] system_call_fastpath+0x1a/0x1f
    Sep 20 22:36:11 mainland kernel: Code: 48 89 55 c8 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 28 4d 85 ed 0f 84 c7 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 5c 05 00 4c 89 e8 65 49
    Sep 20 22:36:11 mainland kernel: RIP [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:36:11 mainland kernel: RSP <ffff88030b555de8>
    Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4c6 ]---
    Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#3] PREEMPT SMP
    Sep 20 22:36:11 mainland kernel: CPU 2
    Sep 20 22:36:11 mainland kernel: Modules linked in:
    Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: Pid: 719, comm: gdbus Tainted: G D 3.5.4-1-ARCH #1
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: /DZ77BH-55K
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff811643fb>]
    Sep 20 22:36:11 mainland kernel: [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff8802fb3f5eb8 EFLAGS: 00010286
    Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: 0000000000000012 RCX: 00000000465a5002
    Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000000d0 RDI: ffffffff811bfeb9
    Sep 20 22:36:11 mainland kernel: RBP: ffff8802fb3f5ef8 R08: 0000000000016710 R09: 0000000000000000
    Sep 20 22:36:11 mainland kernel: R10: 00000000fffffff0 R11: 0000000000000246 R12: 00000000000000d0
    Sep 20 22:36:11 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: 00007f7ac4001e00
    Sep 20 22:36:11 mainland kernel: FS: 00007f7ac8926700(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
    Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep 20 22:36:11 mainland kernel: CR2: 000000000162c580 CR3: 0000000300a56000 CR4: 00000000001407e0
    Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Sep 20 22:36:11 mainland kernel: Process gdbus (pid: 719, threadinfo ffff8802fb3f4000, task ffff8802fe331020)
    Sep 20 22:36:11 mainland kernel: Stack:
    Sep 20 22:36:11 mainland kernel: 0000000000000000
    Sep 20 22:36:11 mainland kernel: 0000000000000030
    Sep 20 22:36:11 mainland kernel: 0000000000000000
    Sep 20 22:36:11 mainland kernel: 0000000000000012
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: 0000000000080800
    Sep 20 22:36:11 mainland kernel: 0000000000000000
    Sep 20 22:36:11 mainland kernel: 00007f7ac4005b80
    Sep 20 22:36:11 mainland kernel: 00007f7ac4001e00
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: ffff8802fb3f5f38
    Sep 20 22:36:11 mainland kernel: ffffffff811bfeb9
    Sep 20 22:36:11 mainland kernel: 00007f7ac89259a8
    Sep 20 22:36:11 mainland kernel: 0000000000dfda80
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: Call Trace:
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: [<ffffffff811bfeb9>] eventfd_file_create+0x49/0xe0
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: [<ffffffff811bff8d>] sys_eventfd2+0x3d/0x80
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: [<ffffffff814853ed>] system_call_fastpath+0x1a/0x1f
    Sep 20 22:36:11 mainland kernel: Code:
    Sep 20 22:36:11 mainland kernel: 48
    Sep 20 22:36:11 mainland kernel: 89
    Sep 20 22:36:11 mainland kernel: 55
    Sep 20 22:36:11 mainland kernel: c8
    Sep 20 22:36:11 mainland kernel: 49
    Sep 20 22:36:11 mainland kernel: 8b
    Sep 20 22:36:11 mainland kernel: 06
    Sep 20 22:36:11 mainland kernel: 65
    Sep 20 22:36:11 mainland kernel: 48
    Sep 20 22:36:11 mainland kernel: 03
    Sep 20 22:36:11 mainland kernel: 04
    Sep 20 22:36:11 mainland kernel: 25
    Sep 20 22:36:11 mainland kernel: e0
    Sep 20 22:36:11 mainland kernel: db
    Sep 20 22:36:11 mainland kernel: 00
    Sep 20 22:36:11 mainland kernel: 00
    Sep 20 22:36:11 mainland kernel: 48
    Sep 20 22:36:11 mainland kernel: 8b
    Sep 20 22:36:11 mainland kernel: 50
    Sep 20 22:36:11 mainland kernel: 08
    Sep 20 22:36:11 mainland kernel: 4c
    Sep 20 22:36:11 mainland kernel: 8b
    Sep 20 22:36:11 mainland kernel: 28
    Sep 20 22:36:11 mainland kernel: 4d
    Sep 20 22:36:11 mainland kernel: 85
    Sep 20 22:36:11 mainland kernel: ed
    Sep 20 22:36:11 mainland kernel: 0f
    Sep 20 22:36:11 mainland kernel: 84
    Sep 20 22:36:11 mainland kernel: c7
    Sep 20 22:36:11 mainland kernel: 00
    Sep 20 22:36:11 mainland kernel: 00
    Sep 20 22:36:11 mainland kernel: 00
    Sep 20 22:36:11 mainland kernel: 49
    Sep 20 22:36:11 mainland kernel: 63
    Sep 20 22:36:11 mainland kernel: 46
    Sep 20 22:36:11 mainland kernel: 20
    Sep 20 22:36:11 mainland kernel: 4d
    Sep 20 22:36:11 mainland kernel: 8b
    Sep 20 22:36:11 mainland kernel: 06
    Sep 20 22:36:11 mainland kernel: 48
    Sep 20 22:36:11 mainland kernel: 8d
    Sep 20 22:36:11 mainland kernel: 4a
    Sep 20 22:36:11 mainland kernel: 40
    Sep 20 22:36:11 mainland kernel: <49>
    Sep 20 22:36:11 mainland kernel: 8b
    Sep 20 22:36:11 mainland kernel: 5c
    Sep 20 22:36:11 mainland kernel: 05
    Sep 20 22:36:11 mainland kernel: 00
    Sep 20 22:36:11 mainland kernel: 4c
    Sep 20 22:36:11 mainland kernel: 89
    Sep 20 22:36:11 mainland kernel: e8
    Sep 20 22:36:11 mainland kernel: 65
    Sep 20 22:36:11 mainland kernel: 49
    Sep 20 22:36:11 mainland kernel: 0f
    Sep 20 22:36:11 mainland kernel: c7
    Sep 20 22:36:11 mainland kernel: 08
    Sep 20 22:36:11 mainland kernel: 0f
    Sep 20 22:36:11 mainland kernel: 94
    Sep 20 22:36:11 mainland kernel: c0
    Sep 20 22:36:11 mainland kernel: 84
    Sep 20 22:36:11 mainland kernel: c0
    Sep 20 22:36:11 mainland kernel: 74
    Sep 20 22:36:11 mainland kernel: c5
    Sep 20 22:36:11 mainland kernel: 49
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: RIP
    Sep 20 22:36:11 mainland kernel: [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:36:11 mainland kernel: RSP <ffff8802fb3f5eb8>
    Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4c7 ]---
    Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#4] PREEMPT SMP
    Sep 20 22:36:11 mainland kernel: CPU 2
    Sep 20 22:36:11 mainland kernel: Modules linked in:
    Sep 20 22:36:11 mainland pulseaudio[4003]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
    Sep 20 22:36:11 mainland pulseaudio[4004]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
    Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: Pid: 1967, comm: threaded-ml Tainted: G D 3.5.4-1-ARCH #1 /DZ77BH-55K
    Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff811643fb>] [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff8802533afe08 EFLAGS: 00010286
    Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: ffff8802b7ac5680 RCX: 00000000465a5002
    Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000000d0 RDI: ffffffff81369ca4
    Sep 20 22:36:11 mainland kernel: RBP: ffff8802533afe48 R08: 0000000000016710 R09: 0000000000000000
    Sep 20 22:36:11 mainland kernel: R10: 00007f10d9cf7278 R11: 0000000000000202 R12: 00000000000000d0
    Sep 20 22:36:11 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: 00007f10b0595a48
    Sep 20 22:36:11 mainland kernel: FS: 00007f10d9cf8700(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
    Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep 20 22:36:11 mainland kernel: CR2: 00007f1102256000 CR3: 00000002fb09c000 CR4: 00000000001407e0
    Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Sep 20 22:36:11 mainland kernel: Process threaded-ml (pid: 1967, threadinfo ffff8802533ae000, task ffff880255b51830)
    Sep 20 22:36:11 mainland kernel: Stack:
    Sep 20 22:36:11 mainland kernel: ffff8802533afec8 0000000000000040 0000000000810010 ffff8802b7ac5680
    Sep 20 22:36:11 mainland kernel: ffff88030d079800 0000000000000000 0000000000000000 00007f10b0595a48
    Sep 20 22:36:11 mainland kernel: ffff8802533afe68 ffffffff81369ca4 0000000000000001 ffff88030d079800
    Sep 20 22:36:11 mainland kernel: Call Trace:
    Sep 20 22:36:11 mainland kernel: [<ffffffff81369ca4>] sock_alloc_inode+0x44/0xd0
    Sep 20 22:36:11 mainland kernel: [<ffffffff811927d6>] alloc_inode+0x26/0xa0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8119400a>] new_inode_pseudo+0x1a/0x70
    Sep 20 22:36:11 mainland kernel: [<ffffffff8136bb0e>] sock_alloc+0x1e/0x80
    Sep 20 22:36:11 mainland kernel: [<ffffffff8136c6fd>] __sock_create+0x9d/0x240
    Sep 20 22:36:11 mainland kernel: [<ffffffff8136c900>] sock_create+0x30/0x40
    Sep 20 22:36:11 mainland kernel: [<ffffffff8136cecb>] sys_socket+0x2b/0x70
    Sep 20 22:36:11 mainland kernel: [<ffffffff8114650b>] ? sys_munmap+0x2b/0x40
    Sep 20 22:36:11 mainland kernel: [<ffffffff814853ed>] system_call_fastpath+0x1a/0x1f
    Sep 20 22:36:11 mainland kernel: Code: 48 89 55 c8 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 28 4d 85 ed 0f 84 c7 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 5c 05 00 4c 89 e8 65 49
    Sep 20 22:36:11 mainland kernel: RIP [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:36:11 mainland kernel: RSP <ffff8802533afe08>
    Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4c8 ]---
    Sep 20 22:36:11 mainland systemd[1]: Unit upower.service entered failed state.
    Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#5] PREEMPT SMP
    Sep 20 22:36:11 mainland kernel: CPU 2
    Sep 20 22:36:11 mainland kernel: Modules linked in:
    Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: Pid: 2, comm: kthreadd Tainted: G D 3.5.4-1-ARCH #1 /DZ77BH-55K
    Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff811643fb>] [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff88030d4e5c90 EFLAGS: 00010286
    Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: ffff88030988f240 RCX: 00000000465a5002
    Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 00000000000000d0 RDI: ffffffff8107c7d6
    Sep 20 22:36:11 mainland kernel: RBP: ffff88030d4e5cd0 R08: 0000000000016710 R09: 00000000ffffffff
    Sep 20 22:36:11 mainland kernel: R10: fffffffffffffffe R11: ffffffffffffffc0 R12: 00000000000000d0
    Sep 20 22:36:11 mainland kernel: R13: ff333333ff333333 R14: ffff880312002700 R15: ffff8802fe32c000
    Sep 20 22:36:11 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
    Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    Sep 20 22:36:11 mainland kernel: CR2: 00007f1102256000 CR3: 000000030bf52000 CR4: 00000000001407e0
    Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Sep 20 22:36:11 mainland kernel: Process kthreadd (pid: 2, threadinfo ffff88030d4e4000, task ffff88030d4d8810)
    Sep 20 22:36:11 mainland kernel: Stack:
    Sep 20 22:36:11 mainland kernel: ffff88030d4d8810 0000000000000030 ffff88030d4e5cb0 ffff88030988f240
    Sep 20 22:36:11 mainland kernel: ffff8802f87de0c0 0000000000800711 ffff8802f87de0c0 ffff8802fe32c000
    Sep 20 22:36:11 mainland kernel: ffff88030d4e5d10 ffffffff8107c7d6 ffff88030d4d8858 0000000000000001
    Sep 20 22:36:11 mainland kernel: Call Trace:
    Sep 20 22:36:11 mainland kernel: [<ffffffff8107c7d6>] copy_creds+0xb6/0x1e0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8104f8c9>] copy_process.part.21+0x289/0x1530
    Sep 20 22:36:11 mainland kernel: [<ffffffff81050cf5>] do_fork+0x135/0x3a0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8101d4f6>] kernel_thread+0x76/0x80
    Sep 20 22:36:11 mainland kernel: [<ffffffff81074ee0>] ? kthread_freezable_should_stop+0x70/0x70
    Sep 20 22:36:11 mainland kernel: [<ffffffff81486860>] ? gs_change+0x13/0x13
    Sep 20 22:36:11 mainland kernel: [<ffffffff810753f0>] kthreadd+0x120/0x160
    Sep 20 22:36:11 mainland kernel: [<ffffffff810814c9>] ? finish_task_switch+0x49/0xe0
    Sep 20 22:36:11 mainland kernel: [<ffffffff81486864>] kernel_thread_helper+0x4/0x10
    Sep 20 22:36:11 mainland kernel: [<ffffffff810752d0>] ? tsk_fork_get_node+0x30/0x30
    Sep 20 22:36:11 mainland kernel: [<ffffffff81486860>] ? gs_change+0x13/0x13
    Sep 20 22:36:11 mainland kernel: Code: 48 89 55 c8 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 28 4d 85 ed 0f 84 c7 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 5c 05 00 4c 89 e8 65 49
    Sep 20 22:36:11 mainland kernel: RIP [<ffffffff811643fb>] kmem_cache_alloc_trace+0x4b/0x150
    Sep 20 22:36:11 mainland kernel: RSP <ffff88030d4e5c90>
    Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4c9 ]---
    Sep 20 22:36:11 mainland kernel: general protection fault: 0000 [#6] PREEMPT SMP
    Sep 20 22:36:11 mainland kernel: CPU 2
    Sep 20 22:36:11 mainland kernel: Modules linked in:
    Sep 20 22:36:11 mainland kernel: fuse w83627ehf hwmon_vid snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support hid_logitech_dj nls_cp437 vfat fat hid_generic usbhid hid microcode ae
    Sep 20 22:36:11 mainland kernel:
    Sep 20 22:36:11 mainland kernel: Pid: 84, comm: kworker/u:6 Tainted: G D 3.5.4-1-ARCH #1 /DZ77BH-55K
    Sep 20 22:36:11 mainland kernel: RIP: 0010:[<ffffffff81163f72>] [<ffffffff81163f72>] __kmalloc+0x62/0x180
    Sep 20 22:36:11 mainland kernel: RSP: 0018:ffff88030b20fb20 EFLAGS: 00010286
    Sep 20 22:36:11 mainland kernel: RAX: 0000000000000000 RBX: ffff8802fb1a4390 RCX: 00000000465a5002
    Sep 20 22:36:11 mainland kernel: RDX: 00000000465a4fc2 RSI: 0000000000000000 RDI: ffffffff81250236
    Sep 20 22:36:11 mainland kernel: RBP: ffff88030b20fb60 R08: 0000000000016710 R09: ffff880312018000
    Sep 20 22:36:11 mainland kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000080d0
    Sep 20 22:36:11 mainland kernel: R13: 0000000000000024 R14: ffff880312002700 R15: ff333333ff333333
    Sep 20 22:36:11 mainland kernel: FS: 0000000000000000(0000) GS:ffff88031ec80000(0000) knlGS:0000000000000000
    Sep 20 22:36:11 mainland kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    Sep 20 22:36:11 mainland kernel: CR2: 00007f1102256000 CR3: 000000000380c000 CR4: 00000000001407e0
    Sep 20 22:36:11 mainland kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Sep 20 22:36:11 mainland kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Sep 20 22:36:11 mainland kernel: Process kworker/u:6 (pid: 84, threadinfo ffff88030b20e000, task ffff88030d7b60c0)
    Sep 20 22:36:11 mainland kernel: Stack:
    Sep 20 22:36:11 mainland kernel: ffff88030b20fb50 ffffffff811648ec ffff88030b20fb50 ffff8802fb1a4390
    Sep 20 22:36:11 mainland kernel: 0000000000000024 0000000000000000 00000000000000d0 ffff880309970d80
    Sep 20 22:36:11 mainland kernel: ffff88030b20fb90 ffffffff81250236 ffff8802fb1a4390 0000000000000001
    Sep 20 22:36:11 mainland kernel: Call Trace:
    Sep 20 22:36:11 mainland kernel: [<ffffffff811648ec>] ? kfree+0x2c/0x150
    Sep 20 22:36:11 mainland kernel: [<ffffffff81250236>] kobject_get_path+0x56/0xc0
    Sep 20 22:36:11 mainland kernel: [<ffffffff81250ffb>] kobject_uevent_env+0xfb/0x4b0
    Sep 20 22:36:11 mainland kernel: [<ffffffff813aa09e>] ? netlink_broadcast_filtered+0x11e/0x3d0
    Sep 20 22:36:11 mainland kernel: [<ffffffff812513bb>] kobject_uevent+0xb/0x10
    Sep 20 22:36:11 mainland kernel: [<ffffffff8124fead>] kobject_release+0x8d/0xa0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8124fd2c>] kobject_put+0x2c/0x60
    Sep 20 22:36:11 mainland kernel: [<ffffffff813989c8>] net_rx_queue_update_kobjects+0xa8/0xe0
    Sep 20 22:36:11 mainland kernel: [<ffffffff81398b76>] netdev_unregister_kobject+0x46/0x80
    Sep 20 22:36:11 mainland kernel: [<ffffffff81380b52>] rollback_registered_many+0x1b2/0x260
    Sep 20 22:36:11 mainland kernel: [<ffffffff81380c1b>] unregister_netdevice_many+0x1b/0x80
    Sep 20 22:36:11 mainland kernel: [<ffffffff81383495>] default_device_exit_batch+0xa5/0xf0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8137c183>] ops_exit_list.isra.1+0x53/0x60
    Sep 20 22:36:11 mainland kernel: [<ffffffff8137c9a8>] cleanup_net+0x108/0x1a0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8106effa>] process_one_work+0x12a/0x440
    Sep 20 22:36:11 mainland kernel: [<ffffffff8137c8a0>] ? net_drop_ns+0x50/0x50
    Sep 20 22:36:11 mainland kernel: [<ffffffff8106f85e>] worker_thread+0x12e/0x2d0
    Sep 20 22:36:11 mainland kernel: [<ffffffff8106f730>] ? manage_workers.isra.26+0x1f0/0x1f0
    Sep 20 22:36:11 mainland kernel: [<ffffffff81074f73>] kthread+0x93/0xa0
    Sep 20 22:36:11 mainland kernel: [<ffffffff81486864>] kernel_thread_helper+0x4/0x10
    Sep 20 22:36:11 mainland kernel: [<ffffffff81074ee0>] ? kthread_freezable_should_stop+0x70/0x70
    Sep 20 22:36:11 mainland kernel: [<ffffffff81486860>] ? gs_change+0x13/0x13
    Sep 20 22:36:11 mainland kernel: Code: 48 8b 7d 08 49 8b 06 65 48 03 04 25 e0 db 00 00 48 8b 50 08 4c 8b 38 4d 85 ff 0f 84 cb 00 00 00 49 63 46 20 4d 8b 06 48 8d 4a 40 <49> 8b 1c 07 4c 89 f8 65 49 0f
    Sep 20 22:36:11 mainland kernel: RIP [<ffffffff81163f72>] __kmalloc+0x62/0x180
    Sep 20 22:36:11 mainland kernel: RSP <ffff88030b20fb20>
    Sep 20 22:36:11 mainland kernel: ---[ end trace 6841e94d0f65e4ca ]---
    Sep 20 22:36:11 mainland kernel: BUG: unable to handle kernel paging request at fffffffffffffff8
    ----- Reboot -----
    The panicks i get are quite rare . I checked the memory recently (memtest) and was ok. My motherboard has a firmware problem where it misroutes irqs. Could this be the root to my problems?? And if its not the motherboard FW related to this how can i determine which HW part fails.
    Last edited by 89c51 (2012-09-20 19:50:10)

  • Is it possible to have multiple page sizes and print types in the same pdf?

    Is it really possible to have a pdf which has multiple pages and each of them have pages which are of different page sizes (e.g. letter, A4, A3) and print types (e.g. Simplex, Duplex)???
    Thanks,
    Phoenix

    you can definately do different page sizes by using different master pages. You can set the paper type for each master page in the object>master page palette.

  • Is it possible to reduce/edit the size of the imported video file?

    Hello,
    I noticed the other day that I am nearing half full on my terabyte hard drive. In reflecting on what is on that drive, it occurred to me that there's a lot of footage that was ultimately never used.
    I was wondering whether there is a way to reduce the size of those files after they've been transferred from the camera? It's not that I want to delete the entire file, rather just get rid of some of the footage that was never used, or after closer examination (sound, movement, etc.) will never be used.
    - note* I know this should be done in advance, prior to logging and capturing, but sometimes that bad footage slips through.
    Thanks.
    DG

    RT is correct.
    For some details, see this:
    http://www.kenstone.net/fcphomepage/media_manager_fcp_4balis.html
    It's for FCP4, but the basic concepts are the same in FCP6, with some minor changes in the step-by-step. Read it for the conceptual understanding, then break open your FCP6 manual for the current procedures.

Maybe you are looking for