Determining visible module

I have an application with multiple modules.  One of the modules refreshes its data on a periodic basis.  I only want it to refresh if it is the visible module.  How can I determine if it is the module in use?

Where in your code do you make it visible/invisible?
The module can always check its parents to see if any are visible=false;

Similar Messages

  • Automatic packaging price in price determination(SD-module)

    Hi,
       We have posted a new condition type in the existing procedure and created condition records. But, when we create a delivery the automatic price is not picked up.We want automatic pick up of packaging price in the delivery.
       Is there any exit where we can use to do so?
       I found one named 'USEREXIT_SAVE_DOCUMENT_PREPARE'
    Can anyone one suggest what code to write in that to achieve the requirement.
    Many thanks in advance.
    Regards,
    Dipen

    Well,
    I think any changes related to pricing should be don in USEREXIT_PRICING_PREPARE_TKOMP. Here one need to do changes in XKOMV table.
    But before that, I just want you people to check the STLNR of table KOMV (sequence number assigned to this newly created condition). Because, in SD, it calculates the Net Price in the sequence.
    Regds,
    Sandip.

  • After Effects CC Output Modules on Render Only Machines

    Hi there, I'm having an issue with custom Output Module Templates and my renderfarm:
    After Effects CC 12.0.0.404 (showing as up to date in Creative Cloud)
    Mac OS X 10.8.4 (Latest Mountain Lion version)
    Mac Pro 2.93 GHz 8-Core, Radeon 5870, 32GB RAM and with Blackmagic Decklink Extreme 3D+
    Remote Machines (there are four) are Mac Pros as well (Quad-core, running 10.7.2 with 16GB RAM), using the ae_render_only_node.txt file in their user Documents folder.
    The exact error:
    aerender ERROR: No output module template was found with the given name.
    I am trying to get a renderfarm working with After Effects CC (see exact version above). Unfortunately, I need custom output modules and I can't seem to get the render slaves to recognize them. I found older threads on this exact issue, but no solution was found.
    I am using commandline aerender in OS X terminal to start a render with a basic test scene.
    To simplify things, I have tried testing this on one render slave machine at a time... Same result everywhere.
    Here's what I've tried:
    I exported a .aom file from my main machine (where I have my desired custom Output Modules) and attempted to bring it in on the render slaves. However, because the render slaves are render only, (they have ae_render_only_node.txt in their Documents folder), the ability to import Output Modules is disabled in After Effects (it opens as the After Effects Render Engine, and the Edit>Templates menu is greyed out).
    Next, I thought I'd try copying the main machine's /Users/(user)/Library/Preferences/Adobe/After Effects/12.0 folder over to the render slaves, thinking that would get whatever preference file to them that's needed to define the output modules. No luck. Launched After Effects (which loads as After Effects Render Engine) and reset my disk cache preferences (so they weren't still the main machine's). Tried aerender again... no luck. Same error:
    aerender ERROR: No output module template was found with the given name.
    After that, I thought it would be a good idea to sign out of Adobe Creative Cloud on the main machine, and try logging into the render slave machine with my full UserID and Password and temporarily remove the ae_render_only_node.txt file. Then, I'd import the .aom file in the full version of AE... I tried this and success! The renders work... they find the Output Modules no problem. Only issue is, as soon as I sign out, and switch to using the ae_render_only_node.txt file, the Output Modules are not found. Not sure what's going on-- if the Output Modules are being disabled by the ae_render_only_node.txt file? Or maybe signing out of my Adobe ID is removing the preferences that determine Output Modules? Don't know where the Output Module preferences are stored to be able to tell.
    Next attempt: I thought I'd try syncing my preferences with Creative Cloud. I made sure to check After Effects Sync Preferences to ensure that Output Modules are set to sync. I did a sync where I uploaded my preferences from the main machine. Then, on the render slaves, I ran Sync Preferences, and chose to download preferences. Works when signed in, but not when used as a render only node. When it's a render only node, it still prompts me to Download the Sync Preferences and Quit the Application, which I do, but nothing seems to happen. I try aerender again, and still the same error:
    aerender ERROR: No output module template was found with the given name.
    I can't seem to find any info on where Output Modules are actually stored (apparently they're not anywhere in the User/Library/Preferences/Adobe/After Effects/ folder?). Are render only nodes not allowed to have custom Output Modules? Not even for something as simple as the Multi-Machine Sequence with a post-render action of Set Proxy enabled?
    Any help is greatly appreciated!
    Thank You.

    I've verified this problem and filed a bug. Sorry about the hiccup.
    I've trying to pin down why this happens, and while I don't have a full explanation yet I think I've stumbled onto a workaround:
    Trash the prefs on the render machine.
    Enable the ae_render_only_node.txt file.
    Launch AE and then quit. <- This is a critical step. More on this later.
    Disable ae_render_only_node.txt file.
    Launch AE.
    Add your Output Module template.
    Quit AE.
    Enable the ae_render_only_node.txt file.
    After you do this, I highly recommend making a backup copy of the Adobe After Effects 12.0 Prefs-indep-output.txt file. Just in case. I've had the failure reappear.
    Now test with aerender and let me know if that works. It has on my machine.
    Why does this matter? When you run AE with the ae_render_only_node.txt file enabled, it appears to add a new section to the preferences: "Output Module Preference Section v28-TRIAL". It's the TRIAL part that is important. Without it, AE doesn't seem to be able to keep track of the OM's when in render_only_node mode. And if you disable the ae_render_only_node.txt file, AE has a tendency to destroy the TRIAL section (I'm still tracing why that happens).
    Now, should this not work for you, I recommend you work around the problem by adding your comps to the render queue in each project. When you do that, and change your aerender flags appropriately, you can render to your desired settings without specifying OMtemplate parameter.
    > I can't seem to find any info on where Output Modules are actually stored (apparently they're not anywhere in the User/Library/Preferences/Adobe/After Effects/ folder?).
    You probably already discovered this. In After Effects CC the OM data is stored in the Adobe After Effects 12.0 Prefs-indep-output.txt file. In older versions of AE, a single pref file such as Adobe After Effects 11.0-x64 Prefs.txt holds all of this data.
    Let me know if that workaround does the trick for you. If I get more information on the cause of the problem I'll update you.

  • Function Module for some sBDOC does not work on

    Hi Experts,
    We have transported on QA landscape sBDOC definition. For sBDOC CNBCCPCUS602,  CNBCCPCUS603,  CNBCCPCUS604 function module seems to be not the right one, so no message of this BDOC are creted when a site extract is done. Error on smohqueue says: "Could not determine function module for processing AC messages".
    Have You encountered a problem like this?
    BR
    Roberto

    Hi All,
    We resolved the problem re-generating CDB pricing condition table using report CND_MAST_GEN_TRANSFER_OBJECTS.
    BR
    Roberto

  • SAP Early Watch Report - Workload By Application Module

    I'm looking at the above part of the Early Watch Report and have been tasked with trying to figure out what programs/processes make up the various modules it is showing such as PY-US, PT-RC, PA,CATS, Unknown, etc.   Can somebody tell me where the system looks to determine what module a process falls in?  Is it something on the ABAP side or where?

    Hi,
    the data is taken from transaction ST03.
    Select <Expert Mode>. Select the application server and time frame of your choice. Afterwards select <Analysis Views | Transaction Profile | EarlyWatch>.
    This table shows all reports and transaction names, which where run in the system in the respective time frame. If you now choose <Aggregation | Application/Subapplication>, you should find a list which fits to the respective chapter in the report. By double-clicking on the specific application name you should also find a list with the according line items for reports and transaction names.
    Best Regards, Vital

  • Subform(s) visibility

    I'm trying to make visible a specific subform based on the value of a radio button. This involves two subforms - stdLayout and customLayout.
    Right now, stdLayout is visible when the form opens while customLayout is invisible.
    I have this code in place now:
    Form initialize:
    customLayout.presence = "invisible";
    Radio button change:
    if (this.rawValue == 1) {
    customLayout.presence = "visible";
    }else{
    customLayout.presence = "invisible";
    This works fine to make customLayout visible, but I'm at a loss for code to make stdLayout INVISIBLE at the same time. Obviously I only want one visible at any time.
    Any help is GREATLY appreciated!
    Thanks
    Mike

    Hello, I just joined the forum today. I am new to this app (v.8) and am learning to create a form. I have a question that looks like it belongs in this thread.
    Here's my situation: the company is finally setting up an intranet, and we are slowly moving to .pdf file distribution instead of MS Word. I'm going through an employee status change form done in Word, using document protection and text fields, checkboxes, drop-downs, etc., and I'm re-creating it in LiveCycle.
    That part was easy, and I learned the basics of the app, but now I want to make a leap to another level. This form tracks access to various systems and apps, which varies according to the division of the business that the employee is in. When I createds all the checkboxes and drop-downs, etc., I clustered them into subforms.
    This thread asks about a radio button value determining subform visibility. I'd like to know if a value in a drop-down can determine visibility. Our hope is that when HR chooses a value in the Division drop-down, then the form will only display the systems and apps that a person in that division would normally have access to.
    Can this be done? and where are you entering that code you sampled here?
    Thanks,
    - A

  • The detail module has disappeared from my tool panel in Lightroom 5. [was:Wolfshooter]

    The detail module has disappeard from my tool panel in lightroom 5.  How do I get it back?

    Right-click near the name of a visible module and reselect "Develop".

  • Why do multiple PXI modules in a chassis cause my PC to continuall​y reset?

    I have a PXI-1000 connected to my desktop PC via a MXI-3 interface. When I plug more than a couple of PXI modules into the chassis and switch on, my PC continually resets itself. Any idea what is wrong?

    Dear Darren,
    This sounds like there is a problem with your chassis supplying the power required for all of your PXI modules. This could indicate either a problem with the power supply on the chassis itself, a problem with the PXI backplane being shorted, or a problem with one or more of your modules. If possible, I recommend testing this system with a different PXI chassis.
    If a second chassis works, then we know the problem is with the first chassis. In this case, I recommend checking for bent pins on the backplane. You can also send it in for repair.
    If the second chassis does not work, then we know the problem probably is not with the chassis. I recommend testing each card. One of your modules could be shorting the backplane. I recommend testing the s
    ystem with each module one at a time. Place each module in each slot in the chassis to see if any combination of modules and slots makes a difference. Once you verify that each module works, you can then test to see if a certain combination of modules causes the problem. The goal here is to determine which module or modules is causing the problem. We need to find out which module is either shorting out the backplane or is drawing too much power.
    This could also be a problem with the MXI-3 connection or the PC. I recommend testing this system with a different PC. You may also consider upgrading your PC's BIOS.
    If you want to send in your chassis or PXI modules for repair, you will need to call in. In this case, go to http://www.ni.com/support and generate a phone support request.
    Regards,
    David Shatila
    Applications Engineer
    National Instruments

  • Module to which a table belongs to

    Hi all,
        How do we determine to which module a table belongs to?
    Ex: Having gone thru SAP docs I know that MARA is a part of MM module. But is it possible to look at the an attribute in a table and determine the module to which it belongs to?

    Hi Sam,
    I don't think we can find out what is the module directly by looking at a table.
    But there is an indirect way. You can open the table in SE11, go to the Attributes tab and check the package.
    E.g. for VBAK, package is VA and a description 'Application development R/3 Sales' is given next to it.
    Similarly for MARA, package is MG and a description 'Application development R/3 material master' is given.
    Hope this helps.
    Regards,
    Sameer

  • Which products/modules 4 auditing/testing current SOD & process controls ?

    What GRC modules and products will i need to test and audit (functional only):
    i) key controls of business process (P2P, O2C etc)
    ii) SOD (segregation of duties) violations for various users
    iii) core business cycles (inventory, expenditure, revenue etc)

    What GRC modules and products will i need to test and audit (functional only):
    i) key controls of business process (P2P, O2C etc) - All the GRC modules starting with eGRCM for all your documentation and test cycles, AACG,PCG, and CCG & TCG for continuous control monitoring
    ii) SOD (segregation of duties) violations for various users - AACG
    iii) core business cycles (inventory, expenditure, revenue etc) - All the GRC modules starting with eGRCM for all your documentation and test cycles, AACG,PCG, and CCG & TCG for continuous control monitoring
    My first approach will e the testing objectives to determine what module will be appropriate. Again, all GRC modules help complement each other understanding the products and how they can be leverage will address all your questions in detail.
    I hope the information above is helpful.
    Thanks,

  • Strange modules initialization

    Hi,
    For some reason strange things appear in everything.log when I startup:
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'ssb:v4243id0807rev03' is not a valid module or alias name
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'pci:v000010DEd000002F0sv000010DEsd000002F0bc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'pci:v000010DEd000002FAsv000010DEsd000002FAbc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'pci:v000010DEd000002FEsv000010DEsd000002FEbc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'pci:v000010DEd000002F8sv000010DEsd000002F8bc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
    Jul  5 12:29:33 E2003WSV load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v000010DEd000002F9sv000010DEsd000002F9bc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v000010DEd000002FFsv000010DEsd000002FFbc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v000010DEd0000027Fsv000010DEsd0000027Fbc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v000010DEd0000027Esv000010DEsd0000027Ebc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v000010DEd00000260sv00001028sd000001F4bc06sc01i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v000010DEd00000270sv000010DEsd0000CB84bc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v000010DEd00000272sv00001028sd000001F4bc05sc00i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v00001022d00001102sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v00001022d00001101sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'platform:vesafb' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v000010DEd0000026Fsv00000000sd00000000bc06sc04i01' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'pci:v00001022d00001100sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
    Jul  5 12:29:34 E2003WSV load-modules.sh: Not loading module 'pcspkr' for alias 'platform:pcspkr' because it is blacklisted
    Jul  5 12:29:34 E2003WSV load-modules.sh: 'ssb:v4243id0807rev03' is not a valid module or alias name
    Obviously there is some config file which determines which modules are loaded, and which for some reason include all these non-existing modules, How can I fix this?

    Yes there are three more files, but none of those include references to "invalid modules or alias names":
    usb-load-ehci-first.conf
    install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install ohci_hcd $CMDLINE_OPTS
    install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install uhci_hcd $CMDLINE_OPTS
    50-sound.conf
    alias snd-card-0 snd-hda-intel
    alias sound-slot-0 snd-hda-intel
    framebuffer_blacklist.conf
    blacklist kyrofb
    blacklist viafb
    blacklist tridentfb
    blacklist tdfxfb
    blacklist cyblafb
    blacklist uvesafb
    blacklist savagefb
    blacklist pm2fb
    blacklist radeonfb
    blacklist atyfb
    blacklist aty128fb
    blacklist s3fb
    blacklist cyber2000fb
    blacklist vmlfb
    blacklist nvidiafb
    blacklist cirrusfb
    blacklist sstfb
    blacklist sisfb
    blacklist i810fb
    blacklist neofb
    blacklist vt8623fb
    blacklist intelfb
    blacklist rivafb
    Last edited by anadyr (2009-07-05 16:34:10)

  • Loading Modules [FAIL] after updating to kernel 2.6.39

    During startup, I see that the Loading Modules part fails. It was doing just fine prior to the update. I fear that some modules are not loaded. So I want to know:
    (1) How to fix this
    (2) How to determine which module failed
    Thanks.

    I get the same problem at boot time (see a FAIL while loading modules) however,
    modprobe -av "list of modules"
    reports no problems. The list of modules I used is the same as in rc.conf in the MODULES directive, as shown below
    MODULES=(ac battery button processor thermal video cdrom intel-agp intel-gtt tpm_bios tpm tpm_tis tpm_tis dcdbas i2c-i801 i2c-core evdev joydev pcspkr psmouse serio_raw sparse-keymap memstick r592 mmc_core sdhci sdhci-pci pci_hotplug shpchp dell-laptop dell-wmi wmi nvidia iTCO_vendor_support iTCO_wdt crc-itu-t snd-hwdep snd snd-page-alloc snd-pcm snd-timer snd-hda-codec snd-hda-intel soundcore scsi_mod ata_piix libphy tg3 mac80211 rfkill iwl3945 iwl-legacy cfg80211 usbcore ehci-hcd uhci-hcd option usbserial usb_wwan firewire-core firewire-ohci sd_mod sr_mod st sg)
    Loading modules automatically was disabled in rc.conf; thus, these modules should be the only ones being loaded at boot time.
    Looked at syslog.log but found no issues. Here is a copy of kernel.log for reference:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Initializing cgroup subsys cpuset
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Initializing cgroup subsys cpu
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Linux version 2.6.39-ARCH (tobias@T-POWA-LX) (gcc version 4.6.0 20110603 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Jun 6 22:37:55 CEST 2011
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/82c10fe2-3a79-4aec-ad18-0a94e2adba10 ro
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-provided physical RAM map:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000bfe84c00 (usable)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000bfe84c00 - 00000000c0000000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000fed18000 - 00000000fed1c000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000feda0000 - 00000000feda6000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] NX (Execute Disable) protection: active
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMI 2.4 present.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMI: Dell Inc. Precision M6300 / , BIOS A08 02/28/2008
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] No AGP bridge found
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] last_pfn = 0x140000 max_arch_pfn = 0x400000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] MTRR default type: uncachable
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] MTRR fixed ranges enabled:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 00000-9FFFF write-back
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] A0000-BFFFF uncachable
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] C0000-CFFFF write-protect
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] D0000-EFFFF uncachable
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] F0000-FFFFF write-protect
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] MTRR variable ranges enabled:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0 base 000000000 mask F80000000 write-back
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 1 base 080000000 mask FC0000000 write-back
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 2 base 100000000 mask FC0000000 write-back
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 3 base 0BFF00000 mask FFFF00000 uncachable
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 4 disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 5 disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 6 disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 7 disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] e820 update range: 00000000bff00000 - 0000000100000000 (usable) ==> (reserved)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] last_pfn = 0xbfe84 max_arch_pfn = 0x400000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] initial memory mapped : 0 - 20000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] init_memory_mapping: 0000000000000000-00000000bfe84000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0000000000 - 00bfe00000 page 2M
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 00bfe00000 - 00bfe84000 page 4k
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] kernel direct mapping tables up to bfe84000 @ bfe7f000-bfe84000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] init_memory_mapping: 0000000100000000-0000000140000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0100000000 - 0140000000 page 2M
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] kernel direct mapping tables up to 140000000 @ 13fffa000-140000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] RAMDISK: 37e4a000 - 37ff0000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: RSDP 00000000000fbb60 00024 (v02 DELL )
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: XSDT 00000000bfe86600 00064 (v01 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: FACP 00000000bfe8649c 000F4 (v04 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: DSDT 00000000bfe86c00 05718 (v02 INT430 SYSFexxx 00001001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: FACS 00000000bfe95400 00040
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: HPET 00000000bfe86700 00038 (v01 DELL M08 00000001 ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: APIC 00000000bfe86800 00068 (v01 DELL M08 27D8021C ASL 00000047)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: ASF! 00000000bfe86400 0007E (v32 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: MCFG 00000000bfe867c0 0003E (v16 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: TCPA 00000000bfe86b00 00032 (v01 00000000 ASL 00000000)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: SLIC 00000000bfe8689c 00176 (v01 DELL M08 27D8021C ASL 00000061)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: SSDT 00000000bfe84d7e 004CC (v01 PmRef CpuPm 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] No NUMA configuration found
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Faking a node at 0000000000000000-0000000140000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] NUMA: Using 63 for the hash shift.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Initmem setup node 0 0000000000000000-0000000140000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] NODE_DATA [000000013fffb000 - 000000013fffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] [ffffea0000000000-ffffea00045fffff] PMD -> [ffff88013b600000-ffff88013edfffff] on node 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Zone PFN ranges:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA 0x00000010 -> 0x00001000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA32 0x00001000 -> 0x00100000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Normal 0x00100000 -> 0x00140000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Movable zone start PFN for each node
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] early_node_map[3] active PFN ranges
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0: 0x00000010 -> 0x0000009f
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0: 0x00000100 -> 0x000bfe84
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] 0: 0x00100000 -> 0x00140000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] On node 0 totalpages: 1048083
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA zone: 56 pages used for memmap
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA zone: 5 pages reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA zone: 3922 pages, LIFO batch:0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA32 zone: 14280 pages used for memmap
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] DMA32 zone: 767676 pages, LIFO batch:31
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Normal zone: 3584 pages used for memmap
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Normal zone: 258560 pages, LIFO batch:31
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: PM-Timer IO Port: 0x1008
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: IRQ0 used by override.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: IRQ2 used by override.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: IRQ9 used by override.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Using ACPI (MADT) for SMP configuration information
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] nr_irqs_gsi: 40
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000bfe84000 - 00000000bfe85000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000bfe85000 - 00000000c0000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000c0000000 - 00000000f8000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000f8000000 - 00000000fc000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fc000000 - 00000000fec00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 00000000fec10000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fec10000 - 00000000fed18000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fed18000 - 00000000fed1c000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fed20000 - 00000000fed90000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fed90000 - 00000000feda0000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000feda0000 - 00000000feda6000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000feda6000 - 00000000fee00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee10000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000fee10000 - 00000000ffe00000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PM: Registered nosave memory: 00000000ffe00000 - 0000000100000000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Allocating PCI resources starting at c0000000 (gap: c0000000:38000000)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Booting paravirtualized kernel on bare hardware
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:2 nr_node_ids:1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88013fc00000 s83136 r8192 d23360 u1048576
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] pcpu-alloc: s83136 r8192 d23360 u1048576 alloc=1*2097152
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] pcpu-alloc: [0] 0 1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1030158
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Policy zone: Normal
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Kernel command line: root=/dev/disk/by-uuid/82c10fe2-3a79-4aec-ad18-0a94e2adba10 ro
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Checking aperture...
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] No AGP bridge found
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Memory: 4057320k/5242880k available (4022k kernel code, 1050548k absent, 135012k reserved, 3332k data, 724k init)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Preemptable hierarchical RCU implementation.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] RCU-based detection of stalled CPUs is disabled.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Verbose stalled-CPUs detection is disabled.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] NR_IRQS:2304
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Extended CMOS year: 2000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Console: colour VGA+ 80x25
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] console [tty0] enabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] allocated 33554432 bytes of page_cgroup
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] hpet clockevent registered
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Fast TSC calibration using PIT
    Jun 13 04:03:43 cry-workstation kernel: [ 0.000000] Detected 2793.013 MHz processor.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.003337] Calibrating delay loop (skipped), value calculated using timer frequency.. 5588.77 BogoMIPS (lpj=9310043)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.003503] pid_max: default: 32768 minimum: 301
    Jun 13 04:03:43 cry-workstation kernel: [ 0.003677] Security Framework initialized
    Jun 13 04:03:43 cry-workstation kernel: [ 0.003763] AppArmor: AppArmor disabled by boot time parameter
    Jun 13 04:03:43 cry-workstation kernel: [ 0.006821] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.009196] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.010435] Mount-cache hash table entries: 256
    Jun 13 04:03:43 cry-workstation kernel: [ 0.010889] Initializing cgroup subsys ns
    Jun 13 04:03:43 cry-workstation kernel: [ 0.010975] ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011075] Initializing cgroup subsys cpuacct
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011182] Initializing cgroup subsys memory
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011279] Initializing cgroup subsys devices
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011362] Initializing cgroup subsys freezer
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011444] Initializing cgroup subsys net_cls
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011527] Initializing cgroup subsys blkio
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011659] CPU: Physical Processor ID: 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011741] CPU: Processor Core ID: 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011823] mce: CPU supports 6 MCE banks
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011912] CPU0: Thermal monitoring enabled (TM2)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.011997] using mwait in idle threads.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.013001] ACPI: Core revision 20110316
    Jun 13 04:03:43 cry-workstation kernel: [ 0.016678] ftrace: allocating 15966 entries in 63 pages
    Jun 13 04:03:43 cry-workstation kernel: [ 0.020045] Setting APIC routing to flat
    Jun 13 04:03:43 cry-workstation kernel: [ 0.020498] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.055697] CPU0: Intel(R) Core(TM)2 Extreme CPU X7900 @ 2.80GHz stepping 0b
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] Performance Events: PEBS fmt0+, Core2 events, Intel PMU driver.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] PEBS disabled due to CPU errata.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... version: 2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... bit width: 40
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... generic registers: 2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... value mask: 000000ffffffffff
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... max period: 000000007fffffff
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... fixed-purpose events: 3
    Jun 13 04:03:43 cry-workstation kernel: [ 0.056663] ... event mask: 0000000700000003
    Jun 13 04:03:43 cry-workstation kernel: [ 0.073433] NMI watchdog enabled, takes one hw-pmu counter.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.100004] Booting Node 0, Processors #1 Ok.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.100152] smpboot cpu 1: start_ip = 9a000
    Jun 13 04:03:43 cry-workstation kernel: [ 0.196685] NMI watchdog enabled, takes one hw-pmu counter.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.203324] Brought up 2 CPUs
    Jun 13 04:03:43 cry-workstation kernel: [ 0.203406] Total of 2 processors activated (11176.50 BogoMIPS).
    Jun 13 04:03:43 cry-workstation kernel: [ 0.204478] devtmpfs: initialized
    Jun 13 04:03:43 cry-workstation kernel: [ 0.204478] print_constraints: dummy:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.204478] NET: Registered protocol family 16
    Jun 13 04:03:43 cry-workstation kernel: [ 0.204478] ACPI: bus type pci registered
    Jun 13 04:03:43 cry-workstation kernel: [ 0.206759] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.206859] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    Jun 13 04:03:43 cry-workstation kernel: [ 0.213476] PCI: Using configuration type 1 for base access
    Jun 13 04:03:43 cry-workstation kernel: [ 0.213565] dmi type 0xB1 record - unknown flag
    Jun 13 04:03:43 cry-workstation kernel: [ 0.213985] bio: create slab <bio-0> at 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.214148] ACPI: EC: Look up EC in DSDT
    Jun 13 04:03:43 cry-workstation kernel: [ 0.218377] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Jun 13 04:03:43 cry-workstation kernel: [ 0.222494] ACPI: SSDT 00000000bfe95480 00043 (v01 LMPWR DELLLOM 00001001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.222889] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.223102] ACPI: SSDT (null) 00043 (v01 LMPWR DELLLOM 00001001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.223492] ACPI: SSDT 00000000bfe858b4 002C8 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.223903] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.224115] ACPI: SSDT (null) 002C8 (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.224424] ACPI: SSDT 00000000bfe8524a 005E5 (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.224825] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.226655] ACPI: SSDT (null) 005E5 (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.227020] ACPI: SSDT 00000000bfe85b7c 000C4 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.227430] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.227643] ACPI: SSDT (null) 000C4 (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.227929] ACPI: SSDT 00000000bfe8582f 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.228333] ACPI: Dynamic OEM Table Load:
    Jun 13 04:03:43 cry-workstation kernel: [ 0.228546] ACPI: SSDT (null) 00085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.228898] ACPI: Interpreter enabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.228980] ACPI: (supports S0 S3 S4 S5)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.229333] ACPI: Using IOAPIC for interrupt routing
    Jun 13 04:03:43 cry-workstation kernel: [ 0.297804] ACPI: ACPI Dock Station Driver: 1 docks/bays found
    Jun 13 04:03:43 cry-workstation kernel: [ 0.297889] HEST: Table not found.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.297971] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Jun 13 04:03:43 cry-workstation kernel: [ 0.304959] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318603] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318689] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318774] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318872] pci_root PNP0A03:00: host bridge window [mem 0x000d0000-0x000dffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.318969] pci_root PNP0A03:00: host bridge window [mem 0xc0000000-0xf7ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319065] pci_root PNP0A03:00: host bridge window [mem 0xfc000000-0xfebfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319162] pci_root PNP0A03:00: host bridge window [mem 0xfec10000-0xfecfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319259] pci_root PNP0A03:00: host bridge window [mem 0xfed1c000-0xfed1ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319356] pci_root PNP0A03:00: host bridge window [mem 0xfed90000-0xfed9ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319453] pci_root PNP0A03:00: host bridge window [mem 0xfed40000-0xfed44fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319549] pci_root PNP0A03:00: host bridge window [mem 0xfeda7000-0xfedfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319646] pci_root PNP0A03:00: host bridge window [mem 0xfee10000-0xff9fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319743] pci_root PNP0A03:00: host bridge window [mem 0xffc00000-0xffdfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319840] pci_root PNP0A03:00: host bridge window [mem 0x140000000-0x337ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319948] pci 0000:00:00.0: [8086:2a00] type 0 class 0x000600
    Jun 13 04:03:43 cry-workstation kernel: [ 0.319995] pci 0000:00:01.0: [8086:2a01] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320025] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320028] pci 0000:00:01.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320078] pci 0000:00:1a.0: [8086:2834] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320134] pci 0000:00:1a.0: reg 20: [io 0x6f20-0x6f3f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320172] pci 0000:00:1a.1: [8086:2835] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320227] pci 0000:00:1a.1: reg 20: [io 0x6f00-0x6f1f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320280] pci 0000:00:1a.7: [8086:283a] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320303] pci 0000:00:1a.7: reg 10: [mem 0xfed1c400-0xfed1c7ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320390] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320395] pci 0000:00:1a.7: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320424] pci 0000:00:1b.0: [8086:284b] type 0 class 0x000403
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320446] pci 0000:00:1b.0: reg 10: [mem 0xf6ffc000-0xf6ffffff 64bit]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320527] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320531] pci 0000:00:1b.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320558] pci 0000:00:1c.0: [8086:283f] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320642] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320646] pci 0000:00:1c.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320676] pci 0000:00:1c.1: [8086:2841] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320760] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320764] pci 0000:00:1c.1: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320796] pci 0000:00:1c.3: [8086:2845] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320879] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320883] pci 0000:00:1c.3: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320915] pci 0000:00:1c.5: [8086:2849] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.320999] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321003] pci 0000:00:1c.5: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321031] pci 0000:00:1d.0: [8086:2830] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321087] pci 0000:00:1d.0: reg 20: [io 0x6f80-0x6f9f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321125] pci 0000:00:1d.1: [8086:2831] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321180] pci 0000:00:1d.1: reg 20: [io 0x6f60-0x6f7f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321218] pci 0000:00:1d.2: [8086:2832] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321273] pci 0000:00:1d.2: reg 20: [io 0x6f40-0x6f5f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321326] pci 0000:00:1d.7: [8086:2836] type 0 class 0x000c03
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321349] pci 0000:00:1d.7: reg 10: [mem 0xfed1c000-0xfed1c3ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321436] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321441] pci 0000:00:1d.7: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321463] pci 0000:00:1e.0: [8086:2448] type 1 class 0x000604
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321547] pci 0000:00:1f.0: [8086:2811] type 0 class 0x000601
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321658] pci 0000:00:1f.0: quirk: [io 0x1000-0x107f] claimed by ICH6 ACPI/GPIO/TCO
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321758] pci 0000:00:1f.0: quirk: [io 0x1080-0x10bf] claimed by ICH6 GPIO
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321846] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0900 (mask 007f)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.321947] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 0c80 (mask 003f)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322084] pci 0000:00:1f.1: [8086:2850] type 0 class 0x000101
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322100] pci 0000:00:1f.1: reg 10: [io 0x01f0-0x01f7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322111] pci 0000:00:1f.1: reg 14: [io 0x03f4-0x03f7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322123] pci 0000:00:1f.1: reg 18: [io 0x0170-0x0177]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322134] pci 0000:00:1f.1: reg 1c: [io 0x0374-0x0377]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322145] pci 0000:00:1f.1: reg 20: [io 0x6fa0-0x6faf]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322189] pci 0000:00:1f.2: [8086:2828] type 0 class 0x000101
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322210] pci 0000:00:1f.2: reg 10: [io 0x6eb0-0x6eb7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322221] pci 0000:00:1f.2: reg 14: [io 0x6eb8-0x6ebb]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322232] pci 0000:00:1f.2: reg 18: [io 0x6ec0-0x6ec7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322244] pci 0000:00:1f.2: reg 1c: [io 0x6ec8-0x6ecb]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322255] pci 0000:00:1f.2: reg 20: [io 0x6ee0-0x6eef]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322266] pci 0000:00:1f.2: reg 24: [io 0xeff0-0xefff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322300] pci 0000:00:1f.2: PME# supported from D3hot
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322304] pci 0000:00:1f.2: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322319] pci 0000:00:1f.3: [8086:283e] type 0 class 0x000c05
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322335] pci 0000:00:1f.3: reg 10: [mem 0xf6ffbf00-0xf6ffbfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322376] pci 0000:00:1f.3: reg 20: [io 0x10c0-0x10df]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322456] pci 0000:01:00.0: [10de:040d] type 0 class 0x000300
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322475] pci 0000:01:00.0: reg 10: [mem 0xf5000000-0xf5ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322495] pci 0000:01:00.0: reg 14: [mem 0xe0000000-0xefffffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322515] pci 0000:01:00.0: reg 1c: [mem 0xf2000000-0xf3ffffff 64bit]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322528] pci 0000:01:00.0: reg 24: [io 0xdf00-0xdf7f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322541] pci 0000:01:00.0: reg 30: [mem 0xf6e00000-0xf6e1ffff pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322620] pci 0000:00:01.0: PCI bridge to [bus 01-01]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322704] pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322707] pci 0000:00:01.0: bridge window [mem 0xf2000000-0xf6efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322711] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322769] pci 0000:00:1c.0: PCI bridge to [bus 0b-0b]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322856] pci 0000:00:1c.0: bridge window [io 0xf000-0x0000] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322861] pci 0000:00:1c.0: bridge window [mem 0xfff00000-0x000fffff] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.322868] pci 0000:00:1c.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323026] pci 0000:0c:00.0: [8086:4222] type 0 class 0x000280
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323081] pci 0000:0c:00.0: reg 10: [mem 0xf1fff000-0xf1ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323422] pci 0000:0c:00.0: PME# supported from D0 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323435] pci 0000:0c:00.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323504] pci 0000:0c:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323679] pci 0000:00:1c.1: PCI bridge to [bus 0c-0c]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323766] pci 0000:00:1c.1: bridge window [io 0xf000-0x0000] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323770] pci 0000:00:1c.1: bridge window [mem 0xf1f00000-0xf1ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323778] pci 0000:00:1c.1: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323837] pci 0000:00:1c.3: PCI bridge to [bus 0d-0e]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323923] pci 0000:00:1c.3: bridge window [io 0xc000-0xcfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323928] pci 0000:00:1c.3: bridge window [mem 0xf1c00000-0xf1efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.323935] pci 0000:00:1c.3: bridge window [mem 0xf0000000-0xf01fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.324065] pci 0000:09:00.0: [14e4:1674] type 0 class 0x000200
    Jun 13 04:03:43 cry-workstation kernel: [ 0.324095] pci 0000:09:00.0: reg 10: [mem 0xf1bf0000-0xf1bfffff 64bit]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.324231] pci 0000:09:00.0: PME# supported from D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.324237] pci 0000:09:00.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330035] pci 0000:00:1c.5: PCI bridge to [bus 09-09]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330121] pci 0000:00:1c.5: bridge window [io 0xf000-0x0000] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330126] pci 0000:00:1c.5: bridge window [mem 0xf1b00000-0xf1bfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330134] pci 0000:00:1c.5: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330179] pci 0000:03:01.0: [1180:0832] type 0 class 0x000c00
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330195] pci 0000:03:01.0: proprietary Ricoh MMC controller disabled (via firewire function)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330294] pci 0000:03:01.0: MMC cards are now supported by standard SDHCI controller
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330405] pci 0000:03:01.0: reg 10: [mem 0xf1aff800-0xf1afffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330489] pci 0000:03:01.0: supports D1 D2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330491] pci 0000:03:01.0: PME# supported from D0 D1 D2 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330496] pci 0000:03:01.0: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330517] pci 0000:03:01.1: [1180:0822] type 0 class 0x000805
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330538] pci 0000:03:01.1: reg 10: [mem 0xf1aff400-0xf1aff4ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330622] pci 0000:03:01.1: supports D1 D2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330623] pci 0000:03:01.1: PME# supported from D0 D1 D2 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330628] pci 0000:03:01.1: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330648] pci 0000:03:01.2: [1180:0592] type 0 class 0x000880
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330670] pci 0000:03:01.2: reg 10: [mem 0xf1aff600-0xf1aff6ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330754] pci 0000:03:01.2: supports D1 D2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330756] pci 0000:03:01.2: PME# supported from D0 D1 D2 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330761] pci 0000:03:01.2: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330782] pci 0000:03:01.3: [1180:0852] type 0 class 0x000880
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330803] pci 0000:03:01.3: reg 10: [mem 0xf1aff700-0xf1aff7ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330888] pci 0000:03:01.3: supports D1 D2
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330889] pci 0000:03:01.3: PME# supported from D0 D1 D2 D3hot D3cold
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330894] pci 0000:03:01.3: PME# disabled
    Jun 13 04:03:43 cry-workstation kernel: [ 0.330963] pci 0000:00:1e.0: PCI bridge to [bus 03-03] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331051] pci 0000:00:1e.0: bridge window [io 0xf000-0x0000] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331056] pci 0000:00:1e.0: bridge window [mem 0xf1a00000-0xf1afffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331063] pci 0000:00:1e.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331065] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331067] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331069] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331071] pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331073] pci 0000:00:1e.0: bridge window [mem 0xc0000000-0xf7ffffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331075] pci 0000:00:1e.0: bridge window [mem 0xfc000000-0xfebfffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331077] pci 0000:00:1e.0: bridge window [mem 0xfec10000-0xfecfffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331079] pci 0000:00:1e.0: bridge window [mem 0xfed1c000-0xfed1ffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331081] pci 0000:00:1e.0: bridge window [mem 0xfed90000-0xfed9ffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331083] pci 0000:00:1e.0: bridge window [mem 0xfed40000-0xfed44fff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331085] pci 0000:00:1e.0: bridge window [mem 0xfeda7000-0xfedfffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331087] pci 0000:00:1e.0: bridge window [mem 0xfee10000-0xff9fffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331089] pci 0000:00:1e.0: bridge window [mem 0xffc00000-0xffdfffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331091] pci 0000:00:1e.0: bridge window [mem 0x140000000-0x337ffffff] (subtractive decode)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331127] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331268] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331339] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331363] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331393] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331425] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331455] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331483] pci0000:00: Requesting ACPI _OSC control (0x1d)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.331566] Unable to assume _OSC PCIe control. Disabling ASPM
    Jun 13 04:03:43 cry-workstation kernel: [ 0.346067] ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 11) *5
    Jun 13 04:03:43 cry-workstation kernel: [ 0.346589] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *10
    Jun 13 04:03:43 cry-workstation kernel: [ 0.347028] ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 11) *3
    Jun 13 04:03:43 cry-workstation kernel: [ 0.347548] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 11) *3
    Jun 13 04:03:43 cry-workstation kernel: [ 0.348197] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.349186] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.350176] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.351158] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352318] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352418] vgaarb: loaded
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352570] PCI: Using ACPI for IRQ routing
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352652] PCI: pci_cache_line_size set to 64 bytes
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352839] reserve RAM buffer: 000000000009f000 - 000000000009ffff
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352841] reserve RAM buffer: 00000000bfe84c00 - 00000000bfffffff
    Jun 13 04:03:43 cry-workstation kernel: [ 0.352941] NetLabel: Initializing
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353023] NetLabel: domain hash size = 128
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353104] NetLabel: protocols = UNLABELED CIPSOv4
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353197] NetLabel: unlabeled traffic allowed by default
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353323] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353412] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.353754] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    Jun 13 04:03:43 cry-workstation kernel: [ 0.363324] Switching to clocksource hpet
    Jun 13 04:03:43 cry-workstation kernel: [ 0.366464] Switched to NOHz mode on CPU #0
    Jun 13 04:03:43 cry-workstation kernel: [ 0.366550] Switched to NOHz mode on CPU #1
    Jun 13 04:03:43 cry-workstation kernel: [ 0.369169] pnp: PnP ACPI init
    Jun 13 04:03:43 cry-workstation kernel: [ 0.369268] ACPI: bus type pnp registered
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376191] pnp 00:00: [bus 00-ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376193] pnp 00:00: [io 0x0000-0x0cf7 window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376195] pnp 00:00: [io 0x0cf8-0x0cff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376197] pnp 00:00: [io 0x0d00-0xffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376198] pnp 00:00: [mem 0x000a0000-0x000bffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376200] pnp 00:00: [mem 0x000d0000-0x000dffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376202] pnp 00:00: [mem 0xc0000000-0xf7ffffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376203] pnp 00:00: [mem 0xfc000000-0xfebfffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376205] pnp 00:00: [mem 0xfec10000-0xfecfffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376207] pnp 00:00: [mem 0xfed1c000-0xfed1ffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376208] pnp 00:00: [mem 0xfed90000-0xfed9ffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376210] pnp 00:00: [mem 0xfed40000-0xfed44fff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376212] pnp 00:00: [mem 0xfeda7000-0xfedfffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376213] pnp 00:00: [mem 0xfee10000-0xff9fffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376215] pnp 00:00: [mem 0xffc00000-0xffdfffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376216] pnp 00:00: [mem 0x140000000-0x337ffffff window]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376281] pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376304] pnp 00:01: [irq 12]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376323] pnp 00:01: Plug and Play ACPI device, IDs PNP0f13 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376334] pnp 00:02: [io 0x0060]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376336] pnp 00:02: [io 0x0064]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376337] pnp 00:02: [io 0x0062]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376339] pnp 00:02: [io 0x0066]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376343] pnp 00:02: [irq 1]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376364] pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376376] pnp 00:03: [io 0x0070-0x0071]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376381] pnp 00:03: [irq 8]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376382] pnp 00:03: [io 0x0072-0x0077]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376400] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376412] pnp 00:04: [io 0x0061]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376417] pnp 00:04: [io 0x0063]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376418] pnp 00:04: [io 0x0065]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376419] pnp 00:04: [io 0x0067]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376439] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376453] pnp 00:05: [io 0x002e-0x002f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376454] pnp 00:05: [io 0x0c80-0x0caf]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376456] pnp 00:05: [io 0x0cc0-0x0cff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376457] pnp 00:05: [io 0x004e-0x004f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376509] system 00:05: [io 0x0c80-0x0caf] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376594] system 00:05: [io 0x0cc0-0x0cff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376694] system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376707] pnp 00:06: [dma 4]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376709] pnp 00:06: [io 0x0000-0x000f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376710] pnp 00:06: [io 0x0080-0x0085]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376712] pnp 00:06: [io 0x0087-0x008f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376713] pnp 00:06: [io 0x00c0-0x00df]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376714] pnp 00:06: [io 0x0010-0x001f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376716] pnp 00:06: [io 0x0090-0x0091]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376717] pnp 00:06: [io 0x0093-0x009f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376737] pnp 00:06: Plug and Play ACPI device, IDs PNP0200 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376747] pnp 00:07: [io 0x00f0-0x00ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376752] pnp 00:07: [irq 13]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376775] pnp 00:07: Plug and Play ACPI device, IDs PNP0c04 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376802] pnp 00:08: [mem 0xfed00000-0xfed003ff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376838] system 00:08: [mem 0xfed00000-0xfed003ff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.376925] system 00:08: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390722] pnp 00:09: [mem 0xfed40000-0xfed44fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390724] pnp 00:09: [io 0x0cb0-0x0cbb]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390761] system 00:09: [io 0x0cb0-0x0cbb] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390846] system 00:09: [mem 0xfed40000-0xfed44fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.390932] system 00:09: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391564] pnp 00:0a: [io 0x0900-0x097f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391566] pnp 00:0a: [io 0x0092]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391567] pnp 00:0a: [io 0x00b2-0x00b3]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391569] pnp 00:0a: [io 0x0020-0x0021]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391570] pnp 00:0a: [io 0x00a0-0x00a1]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391572] pnp 00:0a: [irq 0 disabled]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391573] pnp 00:0a: [io 0x04d0-0x04d1]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391574] pnp 00:0a: [io 0x1000-0x1005]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391576] pnp 00:0a: [io 0x1008-0x100f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391588] pnp 00:0a: disabling [io 0x1000-0x1005] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391689] pnp 00:0a: disabling [io 0x1008-0x100f] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391833] system 00:0a: [io 0x0900-0x097f] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.391918] system 00:0a: [io 0x04d0-0x04d1] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392006] system 00:0a: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392018] pnp 00:0b: [io 0xf400-0xf4fe]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392020] pnp 00:0b: [io 0x0086]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392021] pnp 00:0b: [io 0x1006-0x1007]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392022] pnp 00:0b: [io 0x100a-0x1059]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392024] pnp 00:0b: [io 0x1080-0x10bf]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392025] pnp 00:0b: [io 0x10c0-0x10df]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392026] pnp 00:0b: [io 0x1010-0x102f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392028] pnp 00:0b: [io 0x0809]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392039] pnp 00:0b: disabling [io 0x1006-0x1007] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392139] pnp 00:0b: disabling [io 0x100a-0x1059] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392240] pnp 00:0b: disabling [io 0x1010-0x102f] because it overlaps 0000:00:1f.0 BAR 13 [io 0x1000-0x107f]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392379] system 00:0b: [io 0xf400-0xf4fe] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392463] system 00:0b: [io 0x1080-0x10bf] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392548] system 00:0b: [io 0x10c0-0x10df] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392632] system 00:0b: [io 0x0809] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.392717] system 00:0b: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400883] pnp 00:0c: [mem 0x00000000-0x0009efff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400885] pnp 00:0c: [mem 0x0009f000-0x0009ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400887] pnp 00:0c: [mem 0x000c0000-0x000cffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400889] pnp 00:0c: [mem 0x000e0000-0x000fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400890] pnp 00:0c: [mem 0x00100000-0xbfe84bff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400892] pnp 00:0c: [mem 0xbfe84c00-0xbfefffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400896] pnp 00:0c: [mem 0xbff00000-0xbfffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400898] pnp 00:0c: [mem 0xffe00000-0xffffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400899] pnp 00:0c: [mem 0xffa00000-0xffbfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400901] pnp 00:0c: [mem 0xfec00000-0xfec0ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400902] pnp 00:0c: [mem 0xfee00000-0xfee0ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400904] pnp 00:0c: [mem 0xfed20000-0xfed3ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400905] pnp 00:0c: [mem 0xfed45000-0xfed8ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400907] pnp 00:0c: [mem 0xfeda0000-0xfeda3fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400908] pnp 00:0c: [mem 0xfeda4000-0xfeda4fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400909] pnp 00:0c: [mem 0xfeda5000-0xfeda5fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400911] pnp 00:0c: [mem 0xfeda6000-0xfeda6fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400912] pnp 00:0c: [mem 0xfed18000-0xfed1bfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400914] pnp 00:0c: [mem 0xf8000000-0xfbffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.400980] system 00:0c: [mem 0x00000000-0x0009efff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401066] system 00:0c: [mem 0x0009f000-0x0009ffff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401152] system 00:0c: [mem 0x000c0000-0x000cffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401238] system 00:0c: [mem 0x000e0000-0x000fffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401323] system 00:0c: [mem 0x00100000-0xbfe84bff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401409] system 00:0c: [mem 0xbfe84c00-0xbfefffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401494] system 00:0c: [mem 0xbff00000-0xbfffffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401580] system 00:0c: [mem 0xffe00000-0xffffffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401665] system 00:0c: [mem 0xffa00000-0xffbfffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401751] system 00:0c: [mem 0xfec00000-0xfec0ffff] could not be reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401836] system 00:0c: [mem 0xfee00000-0xfee0ffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.401921] system 00:0c: [mem 0xfed20000-0xfed3ffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402006] system 00:0c: [mem 0xfed45000-0xfed8ffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402092] system 00:0c: [mem 0xfeda0000-0xfeda3fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402177] system 00:0c: [mem 0xfeda4000-0xfeda4fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402262] system 00:0c: [mem 0xfeda5000-0xfeda5fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402348] system 00:0c: [mem 0xfeda6000-0xfeda6fff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402433] system 00:0c: [mem 0xfed18000-0xfed1bfff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402518] system 00:0c: [mem 0xf8000000-0xfbffffff] has been reserved
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402604] system 00:0c: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402630] pnp: PnP ACPI: found 13 devices
    Jun 13 04:03:43 cry-workstation kernel: [ 0.402712] ACPI: ACPI bus type pnp unregistered
    Jun 13 04:03:43 cry-workstation kernel: [ 0.408756] pci 0000:00:1c.5: BAR 15: assigned [mem 0xc0000000-0xc01fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.408855] pci 0000:00:1c.5: BAR 13: assigned [io 0x2000-0x2fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.408940] pci 0000:00:1c.1: BAR 15: assigned [mem 0xc0200000-0xc03fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409038] pci 0000:00:1c.1: BAR 13: assigned [io 0x3000-0x3fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409123] pci 0000:00:1c.0: BAR 14: assigned [mem 0xc0400000-0xc05fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409210] pci 0000:00:1c.0: BAR 15: assigned [mem 0xc0600000-0xc07fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409308] pci 0000:00:1c.0: BAR 13: assigned [io 0x4000-0x4fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409393] pci 0000:00:01.0: PCI bridge to [bus 01-01]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409477] pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409563] pci 0000:00:01.0: bridge window [mem 0xf2000000-0xf6efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409649] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409748] pci 0000:00:1c.0: PCI bridge to [bus 0b-0b]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409833] pci 0000:00:1c.0: bridge window [io 0x4000-0x4fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.409921] pci 0000:00:1c.0: bridge window [mem 0xc0400000-0xc05fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410023] pci 0000:00:1c.0: bridge window [mem 0xc0600000-0xc07fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410126] pci 0000:00:1c.1: PCI bridge to [bus 0c-0c]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410211] pci 0000:00:1c.1: bridge window [io 0x3000-0x3fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410299] pci 0000:00:1c.1: bridge window [mem 0xf1f00000-0xf1ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410387] pci 0000:00:1c.1: bridge window [mem 0xc0200000-0xc03fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410490] pci 0000:00:1c.3: PCI bridge to [bus 0d-0e]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410575] pci 0000:00:1c.3: bridge window [io 0xc000-0xcfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410664] pci 0000:00:1c.3: bridge window [mem 0xf1c00000-0xf1efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410752] pci 0000:00:1c.3: bridge window [mem 0xf0000000-0xf01fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410854] pci 0000:00:1c.5: PCI bridge to [bus 09-09]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.410939] pci 0000:00:1c.5: bridge window [io 0x2000-0x2fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411027] pci 0000:00:1c.5: bridge window [mem 0xf1b00000-0xf1bfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411116] pci 0000:00:1c.5: bridge window [mem 0xc0000000-0xc01fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411219] pci 0000:00:1e.0: PCI bridge to [bus 03-03]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411302] pci 0000:00:1e.0: bridge window [io disabled]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411389] pci 0000:00:1e.0: bridge window [mem 0xf1a00000-0xf1afffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411477] pci 0000:00:1e.0: bridge window [mem pref disabled]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411575] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411662] pci 0000:00:01.0: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411668] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411756] pci 0000:00:1c.0: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411764] pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411852] pci 0000:00:1c.1: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.411860] pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
    Jun 13 04:03:43 cry-workstation kernel: [ 0.412988] pci 0000:00:1c.3: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.412994] pci 0000:00:1c.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413082] pci 0000:00:1c.5: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413090] pci 0000:00:1e.0: setting latency timer to 64
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413094] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413095] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413097] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413099] pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413101] pci_bus 0000:00: resource 8 [mem 0xc0000000-0xf7ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413103] pci_bus 0000:00: resource 9 [mem 0xfc000000-0xfebfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413104] pci_bus 0000:00: resource 10 [mem 0xfec10000-0xfecfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413106] pci_bus 0000:00: resource 11 [mem 0xfed1c000-0xfed1ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413108] pci_bus 0000:00: resource 12 [mem 0xfed90000-0xfed9ffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413110] pci_bus 0000:00: resource 13 [mem 0xfed40000-0xfed44fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413111] pci_bus 0000:00: resource 14 [mem 0xfeda7000-0xfedfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413113] pci_bus 0000:00: resource 15 [mem 0xfee10000-0xff9fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413115] pci_bus 0000:00: resource 16 [mem 0xffc00000-0xffdfffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413117] pci_bus 0000:00: resource 17 [mem 0x140000000-0x337ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413119] pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413120] pci_bus 0000:01: resource 1 [mem 0xf2000000-0xf6efffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413122] pci_bus 0000:01: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413124] pci_bus 0000:0b: resource 0 [io 0x4000-0x4fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413126] pci_bus 0000:0b: resource 1 [mem 0xc0400000-0xc05fffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413128] pci_bus 0000:0b: resource 2 [mem 0xc0600000-0xc07fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413130] pci_bus 0000:0c: resource 0 [io 0x3000-0x3fff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413132] pci_bus 0000:0c: resource 1 [mem 0xf1f00000-0xf1ffffff]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413133] pci_bus 0000:0c: resource 2 [mem 0xc0200000-0xc03fffff 64bit pref]
    Jun 13 04:03:43 cry-workstation kernel: [ 0.413135] pci_bus 0000:0

  • Sale order- Pricing -Access Sequence

    Hi Gurus,
    While creating Sale order, the price is picked from the Pricing procedure and Condition records maintained.
    In PR00- Material price and Customer-Material special price is maintained in VK11.
    So the system picks Customer Material combination price and the same we can see in the Item level conditions-Analysis for pricing and can also see it fetched record from where.
    So for this Client wants in the following way: POPUP MESSAGE
    At Sale order Warning Message that Price is taken from Which List- Normal Price List or Special Price List for Customer and Material combination
    Is there some way to do this?
    Thanks in Advance.
    Best Regards
    Sri

    Hi,
    U have to take ABAPER HELP  No doubt please use this input if tis use full .
    User Exits For Price Determination
    USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ)
    This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document.
    This user exit is described in detail in the "New fields in pricing" section.
    USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
    This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing.
    This user exit is described in detail in the "New fields in pricing" section.
    USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
    You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals.
    This user exit is also used in order processing.
    USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB)
    You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
    This user exit is also used in order processing.
    USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB)
    You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
    This user exit is also used in order processing.
    USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB)
    You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
    This user exit is also used in order processing.
    USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA)
    You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
    USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA)
    In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
    USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA)
    You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
    USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB)
    This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
    USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB)
    Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
    USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB)
    In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
    USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB)
    You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
    USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB)
    This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
    USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB)
    This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
    USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA)
    You can change the KONV fields for copied price components
    With best regards,
    venkataswamy.y

  • 0x4001100200001005 error while running recovery in pavillion dv2000

    here i m trying 2 completely  format the hard drive and while doing so it shows the error 0x4001100200001005 and tells to contact HP support if problem persists..... is it h/w problem????
    Looking for its quick solution......
    help me out...
    thanks.....

    Errors will be obvious, if you get errors, you will need to check to see how many memory modules are installed, remove all but 1 memory module and re -run the test, if that module passes, take out that module and put in the other one, test it, this is how you find which module is bad if you have more than 1.
    After you determine which module is bad, go to one of these sites and buy a replacement module
    www.crucial.com
    www.kingston.com
    sometimes removing and reinserting memory modules from the socket can correct  modules that test bad but are not, they just had a bad electrical connection in the memory socket.

  • 3870 very messed up artifacts

    I have a a K9A2 Platinum, 6400 Black Edition, 2 X 2 AData PC6400, MSI 3870 with Zalman VF900 cooler, Seagate 500 gig IDE drive, floppy, Phillips DVD Burner (Sata), I have a Scythe Ninja for CPU Cooler, using Vista Ultimate 64 bit.
    I leave the computer on 24/7.  I last used it at lunch time about five hours ago it was fine.  When I arrived home this evening and woke it up.  it had about 20 or 30 thin lines of alternating color on a black background.  I shut it down using the power switch, waited a few seconds and started it up.  It seemed to post just fine I got the initial Vista splash screen and then the same thing.  I am letting it cool it's heels for now, off.
    I automatically suspect the Video Card, but it posted.  In my previous experience a bad card artifacts during post too.
    Anyone have any Ideas.  I won't touch it for two hours to ensure coolness.

    read this
    Quote
    Troubleshooting Memory Errors
    Please be aware that not all errors reported by Memtest86 are due to bad memory. The test implicitly tests the CPU, L1 and L2 caches as well as the motherboard. It is impossible for the test to determine what causes the failure to occur. However, most failures will be due to a problem with memory module. When it is not, the only option is to replace parts until the failure is corrected.
    Once a memory error has been detected, determining the failing SIMM/DIMM module is not a clear cut procedure. With the large number of motherboard vendors and possible combinations of memory slots it would be difficult if not impossible to assemble complete information about how a particular error would map to a failing memory module. However, there are steps that may be taken to determine the failing module. Here are four techniques that you may wish to use:
    1) Removing modules
    This is simplest method for isolating a failing modules, but may only be employed when one or more modules can be removed from the system. By selectively removing modules from the system and then running the test you will be able to find the bad modules. Be sure to note exactly which modules are in the system when the test passes and when the test fails.
    2) Rotating modules
    When none of the modules can be removed then you may wish to rotate modules to find the failing one. This technique can only be used if there are three or more modules in the system. Change the location of two modules at a time. For example put the module from slot 1 into slot 2 and put the module from slot 2 in slot 1. Run the test and if either the failing bit or address changes then you know that the failing module is one of the ones just moved. By using several combinations of module movement you should be able to determine which module is failing.
    3) Replacing modules
    If you are unable to use either of the previous techniques then you are left to selective replacement of modules to find the failure.
    4) Avoiding allocation
    The printing mode for BadRAM patterns is intended to construct boot time parameters for a Linux kernel that is compiled with BadRAM support. This work-around makes it possible for Linux to reliably run with defective RAM. For more information on BadRAM support for Linux, sail to http://home.zonnet.nl/vanrein/badram
    Sometimes memory errors show up due to component incompatibility. A memory module may work fine in one system and not in another. This is not uncommon and is a source of confusion. In these situations the components are not necessarily bad but have marginal conditions that when combined with other components will cause errors.
    There have been numerous reports of errors with only tests 5 and 8 on Athlon systems. Often the memory works in a different system or the vendor insists that it is good. In these cases the memory is not necessarily bad but is not able to operate reliably at Athlon speeds. Sometimes more conservative memory timings on the motherboard will correct these errors. In other cases the only option is to replace the memory with better quality, higher speed memory. Don't buy cheap memory and expect it to work with an Athlon! On occasion test 5/8 errors will occur even with name brand memory and a quality motherboard. These errors are legitimate and should be corrected.
    I am often asked about the reliability of errors reported by Mestest86. In the vast majority of cases errors reported by the test are valid. There are some systems that cause Memtest86 to be confused about the size of memory and it will try to test non-existent memory. This will cause a large number of consecutive addresses to be reported as bad and generally there will be many bits in error. If you have a relatively small number of failing addresses and only one or two bits in error you can be certain that the errors are valid. Also intermittent errors are without exception valid. Frequently memory vendors question if Memtest86 supports their particular memory type or a chipset. Memtest86 is designed to work with all memory types and all chipsets. Only support for ECC requires knowledge of the chipset.
    All valid memory errors should be corrected. It is possible that a particular error will never show up in normal operation. However, operating with marginal memory is risky and can result in data loss and even disk corruption. Even if there is no overt indication of problems you cannot assume that your system is unaffected. Sometimes intermittent errors can cause problems that do not show up for a long time. You can be sure that Murphy will get you if you know about a memory error and ignore it.
    Memtest86 can not diagnose many types of PC failures. For example a faulty CPU that causes Windows to crash will most likely just cause Memtest86 to crash in the same way.
    The quoted text above is obtained from http://www.memtest86.com/

Maybe you are looking for