IE 6 is Killing ME!

Hi,
http://scrimshawcomm.info/test_menu.html
I am trying to create a horizontal menu. It works fine in Firefox and was working in IE.
When I took the width value out of the #menuh ul I lost the inline effect on IE.
It still works in Firefox etc.
If I put a width back on the ul it will display inline (horizontal)
I do not want to set a width, bur rather padding on the #menuh a
Any clues?
Thanks
BB

You still have some missing </li> tags. Don't sweat browser differences until after you've produce valid code.
Here's a helpful tool: http://validator.w3.org/
I'm not sure about IE and padding ATM, but I see this:
<!--[if lt IE 7]>
<style type="text/css" media="screen">
#menuh{float:none;}
body{behavior:url(css/csshover.htc); font-size:100%;}
#menuh ul li{float:left; width: 100%;}
#menuh a{height:1%;font:bold 0.7em/1.4em arial, sans-serif;}
</style>
<![endif]-->
I seem to recall that IE (Microsoft) has trouble understanding basic math. If you still have the problem after fixing the invalid HTML, try changing the width to 99% or something similar.
Also, IE6 & 7 don't support XHTML and your server is sending it as text/html anyway, so I suggest File->Convert->HTML 4.01 Strict. You can set that as your default for New documents, if you want to.
Mark A. Boyd
Keep-On-Learnin' :-)

Similar Messages

  • IPhone 4 - 4.2 upgrade killed visual voicemail

    *iPhone 4 - 4.2 upgrade killed visual voicemail*
    Ok, I upgraded to 4.2 and deleted all previous backups, so I know I'm screwed untill the next update.
    I've synced, backed up, restored from backup and still no "Visual Voicemail".
    My voicemail only works if I restore the phone to original settings. But if I do that, I loose important data in my apps. As soon as I "Restore From Backup" I loose my "Visual Voicemail".
    If I reset my voicemail password with AT&T, I get the screen to set up a new password and greeting in Visual Voicemail. When I go through these steps I get the spinning wheel "Saving".
    It never saves, and I get an alert that says it can't connect to voicemail.
    I can set up voicemail by dialing "1", but then all I see is a blank screen in my "Visual Voicemail".
    I've also tried a full reset of my voicemail with AT&T.
    I even got a new SIM card. That didn't work.
    Can anybody figure this one out???
    -Thanks

    Well, thats the first time I've been told that after a week of phone calls. Maybe it's possible.
    I forgot to backup my phone before I upgraded to 4.2. Oops!
    When I noticed my Visual Voicemail was gone I tried to backup but ran out of memory.
    So I deleted previous backups to make more room. It backed up fine after that.
    I don't think it ran out of memory during the update, but maybe it did.
    Crap!

  • Creative Cloud update to version 2.7.1.418 killed my Windows 8.1 system!

    Earlier tonight, I saw the balloon from Creative Cloud stating that an update was available.  So I installed it.  Half-way during the installation, my windows desktop disappeared.
    I started the task manager and restarted "Explorer.exe".  That made the background reappear, but the taskbar was blank with just the lone Windows 8.1 icon on the very left.  Hovering over the taskbar showed the wait cursor.
    The task manager showed everything was running normally but the desktop was clearly broken.  I checked the directories and everything was as expected.
    So I held my breath and rebooted.  After logging in, the desktop slowly appeared over about 10 minutes, but all the desktop icons were still missing, as were the taskbar icons.  Only a few of the notification icons appeared.
    I then managed to bring up a command window with the task manager (fortunately, Ctrl+Alt+Esc still worked) and launched System Restore (rstrui.exe).  It showed me the Adobe Creative Cloud was the most recent restore point (below); the previous restore point after that was a Microsoft Windows update from 2 days ago.  When I asked for the list of files that were affected by the Creative Cloud update and would be reverted, it showed this:
    I again held my breath and restored my machine to before the above CC update; after about 20 minutes of shucking and jiving and a reboot, everything was working properly again.
    So there is clearly something out of kilter with this latest update.  Adobe the Time Vampire has once again stolen 2 hours of my life, but this time, at least it wasn't a license server issue.  I think.

    Dave: I did the Microsoft Update two days before this happened, and rebooted as required.  I just created a new restore point and lauched Creative Cloud.  Now I get the famous white screen:
    It just sits and spins (been 10 minutes now). 
    Fortunately, I saved away this command (which I've had to use 4 or 5 times already):
    del %USERPROFILE%\AppData\Local\Adobe\OOBE\opm.db
    Unfortunately now, I get this (even after closing the above window):
    The process cannot access the file because it is being used by another process.
    So I killed everything that said "Adobe" in the task manager and this time, the command succeeded.
    Fortunately, the current apps seem to still work.  I can't seem to find the "Creative Cloud" app in the applications on my system, but I launched Photoshop CC, told it to look for updates, and got a list of the 5 prgorams that need updates in the Adobe Application manager:
    I will proceed with the updates, holding my breath.

  • Killing an application running on RT

    Hi
    Am using an PXI -8186 embedded controller with PharLap ETS RTOS, i have downloaded an application on to the RT startup directory. I want to deleted the application as i dont need it, but as it automatically starts running when pxi boots up i am unable to delete it. How can i Kill the application and delete it from startup? The rtos does not have a promt, so i can kill the task or look in to directory.
    I have to use only Ftp. can any one please help.
    thanx
    Arun

    Hello!
    On your 8186 there is a disable start up VI switch. On page 2-12 of the manual you will be able to find the location of this switch. Just incase I have pasted the link to the manual below.
    http://www.ni.com/pdf/manuals/370747c.pdf
    After you disable the start VI you will be able to remove it. Hope this helps. Let me know if I can give you anymore assistance.
    Allan S.
    National Instruments

  • What does it happen if killing app then fast startup?

    Ask this question dues to my app is very likely to crash if I kill the app  then restart it very fast.  My debugging shows that when you double click back button then kill app, you see app really disappear, in fact it is still running, needs some time to exit completely. Then if you start up it very fast, app will re-access original dying app, instead of launch a new process, then it will be very likely to crash.
    It is not difficult to reproduce it on either device or simulator, the reason is my app running under heavy thread pool (C++ boost implementation), normally it will need some time to destroy the pool (waiting all working threads to join).
    I am not sure whether it is system behavior? Does user need to wait for a few seconds after killing app?  Or how can I avoid it on application layer?  Thank you.

    You've posted your question in the iPhoto for iOS forum, but iPhoto for iOS is not compatible with an iPod touch. Are you trying to "edit" an album in the the Photos application?
    -Doug

  • Java API - EventHandler threads not getting killed

    Hello everybody,
    I didn't know whether to post this in the PI forum or in the MDM forum. I use the following scenario:
    We run an EJB session bean in the Java Proxy environment of PI 7.1. In this bean we create an MDM session, log on to a repository and then attach a RecordListener that reacts to any change of the records. When an interesting change took place, the record is distributed to PI.
    The code looks like this:
    EventDispatcher evDis = new EventDispatcher(servername);
    RecordListener recLis = new RecordListener();
    evDis.registerDataNotifications(username, password, repIdent, regions[0]);
    evDis.addListener(recLis);
    The problem arises when we try to undeploy or stop the application. You would assume that it would stop everything connected to the application. However, it does not. The mentioned EventDispatcher creates a thread object when invoked, and this thread is never killed. The consequence: Records keep getting distributed as if nothing had happened, although the application is gone (even undeploying doesn't help). But when we redeploy the application, a new thread is created. So after some development you get 10 or more threads firing every change to PI. The only thing that helps is a restart of the J2EE engine.
    So, my question: Has anybody here made a similar experience? Is this common for MDM or is rather PI the cause of this issue?
    Any comments on that are very welcome.
    Best regards,
    Jörg

    Hi Veera,
    thanks a lot, that pot me on the right track! In fact, it's the @PreDestroy annotation which has to be used for some cleanup method. When we execute this and included the coding you mentioned the threads are killed properly.
    Currently we're facing the issue that somehow the commit status of the bean is not set to "Committed" and from the second message on we get exceptions. If anybody came across this, help is appreciated.
    Best regards,
    Jörg

  • Itunes 6.0.1.3 is killing my network!

    The last time I updated all my podcasts was 12-8-5. I had not run Itunes since then. I fired it up this past weekend and something really strange happened.
    It was unable to update any podcasts. Also, my laptop had disconnected from my wireless network. I closed Itunes but my system still was unable to see any wireless network. I rebooted and was able to connect again. I then left the wireless properties open and started Itunes. My wireless connection began to drop in speed over the course of 1 minute from 54 -> 36 -> 24 -> 11 -> 1 -> 0 Mbps when it again disconnected and would not see wireless. I rebooted and started all over again. This time I closed Itunes before it killed the connection and within 1 minute my speed is back up to 54 Mbps.
    This is also happening on my hardwired Desktop! As soon as I fire up Itunes, the lights on my switch and router and every AP start flashing like crazy! I am talking about three switches and a wireless bridge. The activity lights on all devices go crazy until I kill Itunes on my desktop. As soon as I do, the activity stops, but I am forced to reboot all my network devices to get the network up again.
    No, I am not the only person in the world seeing this behavior. I just listened to Leo Laporte's KFI Tech Guy podcast from the first week of December and a caller was describing the exact same issue:
    http://leoville.tv/radio/ShowNotes/Show201#toc3
    I have also found another reference to the same thing here:
    http://forums.macnn.com/archive/index.php/t-246946.html
    And another here:
    http://groups.google.com/group/microsoft.public.windowsxp.networkweb/browsethread/thread/12be291b47a65868/04144bc0accb23f8#04144bc0accb23f8
    Basically, running Itunes kills my network!
    I have turned off all automatic network functions in Itunes, like automatic podcast updates and search for shared music. Turning off search for shared music seems to have solved the need to reboot every network device in my house, but running Itunes still causes the death of my wireless connection on my notebook.
    I can only postulate that this MUST be the result of a recent XP update since Itunes was working just fine a few weeks ago. To test this theory, I will be doing a parallel OS install of XP SP2 on my laptop with no additional updates and Itunes the only installed application. I might try doing this in Virtual PC first, but I am not sure I could trust its results.

    OK,
    I just installed Itunes 6.0.1.3 on a fresh install of XP SP2 in Virtual PC.
    Simply starting Itunes, No subscriptionsn no podcasts to update, and the same results.
    Within 1 minute, the network connection on the VPC was dead and reported limited or no connectivity. Before it died, the wireless on my laptop began to decrease in speed. As soon as the network connection in VPC died, it began rising again. As with my desktop, my network devices activity lights lit up almost solid! The ethernet bridge that connects my ReplayTV to the network went solid on activity and my Replay was knocked off the network. It would appear the 6.0.1.3 is spewing a bunch of garbage on the network to the point that it is killing all my devices.
    Whenever Itunes is open on any system on the network (In its default config), ALL devices lose network connectivity.
    Now I will try an older version on the virtual PC and see what happens..
    Stephen TN

  • "Kernel panic - not syncing: Attempted to kill init!" on shutdown

    For several years now, I've been happily using Arch. I'm quite a seasoned user. I've solved countless errors and problems with my systems on 3 different machines, but I don't know how to fix this one. I've searched the forum and asked google -- got no answer.
    Since systemd upgrade on my Asus laptop, shutdown and reboot broke down. The other machine with Arch works fine (systemd installed), but that's a stationary computer.
    I don't know what may be wrong... The system is upgraded to the full. The error displayed by kernel is as follows:
    Kernel panic - not syncing: Attempted to kill init!
    And photo of it happening: http://i.imgur.com/kewfbYv.jpg
    This happens every time I try to shut down or reboot the laptop. (I'm using the poweroff and reboot commands). I have to press the power button for a while to force poweroff. It's really annoying.
    Everything works just fine except this kernel panic. I'm using catalyst drivers. Other than that - nothing "unusual".
    Boot journal:
    -- Logs begin at Mon 2012-12-31 05:00:25 CET, end at Sat 2013-01-26 12:27:00 CET. --
    Jan 26 12:20:45 further systemd-journal[145]: Allowing runtime journal files to grow to 171.5M.
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys cpuset
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys cpu
    Jan 26 12:20:45 further kernel: Linux version 3.7.4-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 2013
    Jan 26 12:20:45 further kernel: Command line: root=/dev/sda6 ro nomodeset init=/sbin/init rootfstype=ext4
    Jan 26 12:20:45 further kernel: e820: BIOS-provided physical RAM map:
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x0000000000100000-0x000000008f6bffff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f6c0000-0x000000008f702fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f703000-0x000000008f711fff] ACPI data
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f712000-0x000000008f828fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f829000-0x000000008f838fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f839000-0x000000008f867fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f868000-0x000000008f868fff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f869000-0x000000008f871fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f872000-0x000000008f883fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f884000-0x000000008f891fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f892000-0x000000008f893fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f894000-0x000000008f89afff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f89b000-0x000000008f89dfff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f89e000-0x000000008f8a6fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f8a7000-0x000000008f8cdfff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f8ce000-0x000000008fad0fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008fad1000-0x000000008fd45fff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008fd46000-0x000000008fef6fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008fef7000-0x000000008fefffff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fed61000-0x00000000fed70fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x0000000100001000-0x000000014effffff] usable
    Jan 26 12:20:45 further kernel: NX (Execute Disable) protection: active
    Jan 26 12:20:45 further kernel: DMI 2.7 present.
    Jan 26 12:20:45 further kernel: DMI: ASUSTeK Computer Inc. K43TA/K43TA, BIOS 214 04/06/2012
    Jan 26 12:20:45 further kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Jan 26 12:20:45 further kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Jan 26 12:20:45 further kernel: No AGP bridge found
    Jan 26 12:20:45 further kernel: e820: last_pfn = 0x14f000 max_arch_pfn = 0x400000000
    Jan 26 12:20:45 further kernel: MTRR default type: uncachable
    Jan 26 12:20:45 further kernel: MTRR fixed ranges enabled:
    Jan 26 12:20:45 further kernel: 00000-9FFFF write-back
    Jan 26 12:20:45 further kernel: A0000-BFFFF write-through
    Jan 26 12:20:45 further kernel: C0000-CEFFF write-protect
    Jan 26 12:20:45 further kernel: CF000-E7FFF uncachable
    Jan 26 12:20:45 further kernel: E8000-FFFFF write-protect
    Jan 26 12:20:45 further kernel: MTRR variable ranges enabled:
    Jan 26 12:20:45 further kernel: 0 base 0000000000 mask FF80000000 write-back
    Jan 26 12:20:45 further kernel: 1 base 0080000000 mask FFF0000000 write-back
    Jan 26 12:20:45 further kernel: 2 base 008FF00000 mask FFFFF00000 uncachable
    Jan 26 12:20:45 further kernel: 3 disabled
    Jan 26 12:20:45 further kernel: 4 disabled
    Jan 26 12:20:45 further kernel: 5 disabled
    Jan 26 12:20:45 further kernel: 6 disabled
    Jan 26 12:20:45 further kernel: 7 disabled
    Jan 26 12:20:45 further kernel: TOM2: 000000014f000000 aka 5360M
    Jan 26 12:20:45 further kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Jan 26 12:20:45 further kernel: e820: update [mem 0x8ff00000-0xffffffff] usable ==> reserved
    Jan 26 12:20:45 further kernel: e820: last_pfn = 0x8ff00 max_arch_pfn = 0x400000000
    Jan 26 12:20:45 further kernel: found SMP MP-table at [mem 0x000fce90-0x000fce9f] mapped at [ffff8800000fce90]
    Jan 26 12:20:45 further kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
    Jan 26 12:20:45 further kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
    Jan 26 12:20:45 further kernel: Using GB pages for direct mapping
    Jan 26 12:20:45 further kernel: init_memory_mapping: [mem 0x00000000-0x8fefffff]
    Jan 26 12:20:45 further kernel: [mem 0x00000000-0x7fffffff] page 1G
    Jan 26 12:20:45 further kernel: [mem 0x80000000-0x8fdfffff] page 2M
    Jan 26 12:20:45 further kernel: [mem 0x8fe00000-0x8fefffff] page 4k
    Jan 26 12:20:45 further kernel: kernel direct mapping tables up to 0x8fefffff @ [mem 0x1fffd000-0x1fffffff]
    Jan 26 12:20:45 further kernel: init_memory_mapping: [mem 0x100001000-0x14effffff]
    Jan 26 12:20:45 further kernel: [mem 0x100001000-0x1001fffff] page 4k
    Jan 26 12:20:45 further kernel: [mem 0x100200000-0x14effffff] page 2M
    Jan 26 12:20:45 further kernel: kernel direct mapping tables up to 0x14effffff @ [mem 0x8fefc000-0x8fefffff]
    Jan 26 12:20:45 further kernel: RAMDISK: [mem 0x37d07000-0x37feffff]
    Jan 26 12:20:45 further kernel: ACPI: RSDP 00000000000f0450 00024 (v02 _ASUS_)
    Jan 26 12:20:45 further kernel: ACPI: XSDT 000000008f703068 00054 (v01 _ASUS_ Notebook 01072009 AMI 00010013)
    Jan 26 12:20:45 further kernel: ACPI: FACP 000000008f70f1a0 000F4 (v04 _ASUS_ Notebook 01072009 AMI 00010013)
    Jan 26 12:20:45 further kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20120913/tbfadt-598)
    Jan 26 12:20:45 further kernel: ACPI: DSDT 000000008f703150 0C050 (v02 _ASUS_ Notebook 00000000 INTL 20091112)
    Jan 26 12:20:45 further kernel: ACPI: FACS 000000008f89af80 00040
    Jan 26 12:20:45 further kernel: ACPI: APIC 000000008f70f298 00072 (v03 _ASUS_ Notebook 01072009 AMI 00010013)
    Jan 26 12:20:45 further kernel: ACPI: MCFG 000000008f70f310 0003C (v01 _ASUS_ GMCH945. 01072009 MSFT 00000097)
    Jan 26 12:20:45 further kernel: ACPI: HPET 000000008f70f350 00038 (v01 _ASUS_ Notebook 01072009 AMI 00000004)
    Jan 26 12:20:45 further kernel: ACPI: SSDT 000000008f70f388 00726 (v01 _ASUS_ POWERNOW 00000001 AMD 00000001)
    Jan 26 12:20:45 further kernel: ACPI: SSDT 000000008f70fab0 0190A (v02 _ASUS_ ALIB 00000001 MSFT 04000000)
    Jan 26 12:20:45 further kernel: ACPI: Local APIC address 0xfee00000
    Jan 26 12:20:45 further kernel: No NUMA configuration found
    Jan 26 12:20:45 further kernel: Faking a node at [mem 0x0000000000000000-0x000000014effffff]
    Jan 26 12:20:45 further kernel: Initmem setup node 0 [mem 0x00000000-0x14effffff]
    Jan 26 12:20:45 further kernel: NODE_DATA [mem 0x14effc000-0x14effffff]
    Jan 26 12:20:45 further kernel: [ffffea0000000000-ffffea00053fffff] PMD -> [ffff88014ae00000-ffff88014e5fffff] on node 0
    Jan 26 12:20:45 further kernel: Zone ranges:
    Jan 26 12:20:45 further kernel: DMA [mem 0x00010000-0x00ffffff]
    Jan 26 12:20:45 further kernel: DMA32 [mem 0x01000000-0xffffffff]
    Jan 26 12:20:45 further kernel: Normal [mem 0x100000000-0x14effffff]
    Jan 26 12:20:45 further kernel: Movable zone start for each node
    Jan 26 12:20:45 further kernel: Early memory node ranges
    Jan 26 12:20:45 further kernel: node 0: [mem 0x00010000-0x0009cfff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x00100000-0x8f6bffff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x8f868000-0x8f868fff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x8fad1000-0x8fd45fff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x8fef7000-0x8fefffff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x100001000-0x14effffff]
    Jan 26 12:20:45 further kernel: On node 0 totalpages: 911563
    Jan 26 12:20:45 further kernel: DMA zone: 64 pages used for memmap
    Jan 26 12:20:45 further kernel: DMA zone: 6 pages reserved
    Jan 26 12:20:45 further kernel: DMA zone: 3911 pages, LIFO batch:0
    Jan 26 12:20:45 further kernel: DMA32 zone: 16320 pages used for memmap
    Jan 26 12:20:45 further kernel: DMA32 zone: 567679 pages, LIFO batch:31
    Jan 26 12:20:45 further kernel: Normal zone: 5056 pages used for memmap
    Jan 26 12:20:45 further kernel: Normal zone: 318527 pages, LIFO batch:31
    Jan 26 12:20:45 further kernel: ACPI: PM-Timer IO Port: 0x808
    Jan 26 12:20:45 further kernel: ACPI: Local APIC address 0xfee00000
    Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
    Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
    Jan 26 12:20:45 further kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    Jan 26 12:20:45 further kernel: ACPI: IOAPIC (id[0x03] address[0xfec00000] gsi_base[0])
    Jan 26 12:20:45 further kernel: IOAPIC[0]: apic_id 3, version 33, address 0xfec00000, GSI 0-23
    Jan 26 12:20:45 further kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Jan 26 12:20:45 further kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
    Jan 26 12:20:45 further kernel: ACPI: IRQ0 used by override.
    Jan 26 12:20:45 further kernel: ACPI: IRQ2 used by override.
    Jan 26 12:20:45 further kernel: ACPI: IRQ9 used by override.
    Jan 26 12:20:45 further kernel: Using ACPI (MADT) for SMP configuration information
    Jan 26 12:20:45 further kernel: ACPI: HPET id: 0xffffffff base: 0xfed00000
    Jan 26 12:20:45 further kernel: smpboot: Allowing 4 CPUs, 2 hotplug CPUs
    Jan 26 12:20:45 further kernel: nr_irqs_gsi: 40
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000000009d000 - 000000000009e000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000000009e000 - 00000000000a0000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f6c0000 - 000000008f703000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f703000 - 000000008f712000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f712000 - 000000008f829000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f829000 - 000000008f839000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f839000 - 000000008f868000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f869000 - 000000008f872000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f872000 - 000000008f884000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f884000 - 000000008f892000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f892000 - 000000008f894000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f894000 - 000000008f89b000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f89b000 - 000000008f89e000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f89e000 - 000000008f8a7000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f8a7000 - 000000008f8ce000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f8ce000 - 000000008fad1000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008fd46000 - 000000008fef7000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008ff00000 - 00000000e0000000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000f0000000 - 00000000fec00000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec01000 - 00000000fec10000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec10000 - 00000000fec11000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec11000 - 00000000fed00000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed00000 - 00000000fed01000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed01000 - 00000000fed61000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed61000 - 00000000fed71000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed71000 - 00000000fed80000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed80000 - 00000000fed90000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed90000 - 00000000ff000000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000ff000000 - 0000000100000000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 0000000100000000 - 0000000100001000
    Jan 26 12:20:45 further kernel: e820: [mem 0x8ff00000-0xdfffffff] available for PCI devices
    Jan 26 12:20:45 further kernel: Booting paravirtualized kernel on bare hardware
    Jan 26 12:20:45 further kernel: setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1
    Jan 26 12:20:45 further kernel: PERCPU: Embedded 28 pages/cpu @ffff88014ec00000 s84544 r8192 d21952 u524288
    Jan 26 12:20:45 further kernel: pcpu-alloc: s84544 r8192 d21952 u524288 alloc=1*2097152
    Jan 26 12:20:45 further kernel: pcpu-alloc: [0] 0 1 2 3
    Jan 26 12:20:45 further kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 890117
    Jan 26 12:20:45 further kernel: Policy zone: Normal
    Jan 26 12:20:45 further kernel: Kernel command line: root=/dev/sda6 ro nomodeset init=/sbin/init rootfstype=ext4
    Jan 26 12:20:45 further kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    Jan 26 12:20:45 further kernel: __ex_table already sorted, skipping sort
    Jan 26 12:20:45 further kernel: Checking aperture...
    Jan 26 12:20:45 further kernel: No AGP bridge found
    Jan 26 12:20:45 further kernel: Calgary: detecting Calgary via BIOS EBDA area
    Jan 26 12:20:45 further kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Jan 26 12:20:45 further kernel: Memory: 3508092k/5488640k available (4832k kernel code, 1842388k absent, 138160k reserved, 4077k data, 808k init)
    Jan 26 12:20:45 further kernel: SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    Jan 26 12:20:45 further kernel: Preemptible hierarchical RCU implementation.
    Jan 26 12:20:45 further kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Jan 26 12:20:45 further kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Jan 26 12:20:45 further kernel: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
    Jan 26 12:20:45 further kernel: NR_IRQS:4352 nr_irqs:712 16
    Jan 26 12:20:45 further kernel: Extended CMOS year: 2000
    Jan 26 12:20:45 further kernel: Console: colour VGA+ 80x25
    Jan 26 12:20:45 further kernel: console [tty0] enabled
    Jan 26 12:20:45 further kernel: allocated 14680064 bytes of page_cgroup
    Jan 26 12:20:45 further kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Jan 26 12:20:45 further kernel: hpet clockevent registered
    Jan 26 12:20:45 further kernel: tsc: Fast TSC calibration using PIT
    Jan 26 12:20:45 further kernel: tsc: Detected 1896.600 MHz processor
    Jan 26 12:20:45 further kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3794.25 BogoMIPS (lpj=6322000)
    Jan 26 12:20:45 further kernel: pid_max: default: 32768 minimum: 301
    Jan 26 12:20:45 further kernel: Security Framework initialized
    Jan 26 12:20:45 further kernel: AppArmor: AppArmor disabled by boot time parameter
    Jan 26 12:20:45 further kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
    Jan 26 12:20:45 further kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
    Jan 26 12:20:45 further kernel: Mount-cache hash table entries: 256
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys cpuacct
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys memory
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys devices
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys freezer
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys net_cls
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys blkio
    Jan 26 12:20:45 further kernel: tseg: 008ff00000
    Jan 26 12:20:45 further kernel: CPU: Physical Processor ID: 0
    Jan 26 12:20:45 further kernel: CPU: Processor Core ID: 0
    Jan 26 12:20:45 further kernel: mce: CPU supports 6 MCE banks
    Jan 26 12:20:45 further kernel: [120B blob data]
    Jan 26 12:20:45 further kernel: Freeing SMP alternatives: 16k freed
    Jan 26 12:20:45 further kernel: ACPI: Core revision 20120913
    Jan 26 12:20:45 further kernel: ftrace: allocating 18585 entries in 73 pages
    Jan 26 12:20:45 further kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Jan 26 12:20:45 further kernel: smpboot: CPU0: AMD A4-3300M APU with Radeon(tm) HD Graphics (fam: 12, model: 01, stepping: 00)
    Jan 26 12:20:45 further kernel: Performance Events: AMD PMU driver.
    Jan 26 12:20:45 further kernel: ... version: 0
    Jan 26 12:20:45 further kernel: ... bit width: 48
    Jan 26 12:20:45 further kernel: ... generic registers: 4
    Jan 26 12:20:45 further kernel: ... value mask: 0000ffffffffffff
    Jan 26 12:20:45 further kernel: ... max period: 00007fffffffffff
    Jan 26 12:20:45 further kernel: ... fixed-purpose events: 0
    Jan 26 12:20:45 further kernel: ... event mask: 000000000000000f
    Jan 26 12:20:45 further kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Jan 26 12:20:45 further kernel: smpboot: Booting Node 0, Processors #1
    Jan 26 12:20:45 further kernel: Brought up 2 CPUs
    Jan 26 12:20:45 further kernel: smpboot: Total of 2 processors activated (7589.50 BogoMIPS)
    Jan 26 12:20:45 further kernel: devtmpfs: initialized
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f6c0000-0x8f702fff] (274432 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f829000-0x8f838fff] (65536 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f869000-0x8f871fff] (36864 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f884000-0x8f891fff] (57344 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f894000-0x8f89afff] (28672 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f89e000-0x8f8a6fff] (36864 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f8ce000-0x8fad0fff] (2109440 bytes)
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 16
    Jan 26 12:20:45 further kernel: ACPI: bus type pci registered
    Jan 26 12:20:45 further kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    Jan 26 12:20:45 further kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    Jan 26 12:20:45 further kernel: PCI: Using configuration type 1 for base access
    Jan 26 12:20:45 further kernel: bio: create slab <bio-0> at 0
    Jan 26 12:20:45 further kernel: ACPI: Added _OSI(Module Device)
    Jan 26 12:20:45 further kernel: ACPI: Added _OSI(Processor Device)
    Jan 26 12:20:45 further kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Jan 26 12:20:45 further kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Jan 26 12:20:45 further kernel: ACPI: EC: Look up EC in DSDT
    Jan 26 12:20:45 further kernel: ACPI: Executed 1 blocks of module-level executable AML code
    Jan 26 12:20:45 further kernel: ACPI: Interpreter enabled
    Jan 26 12:20:45 further kernel: ACPI: (supports S0 S3 S4 S5)
    Jan 26 12:20:45 further kernel: ACPI: Using IOAPIC for interrupt routing
    Jan 26 12:20:45 further kernel: [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
    Jan 26 12:20:45 further kernel: [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
    Jan 26 12:20:45 further kernel: ACPI: EC: GPE = 0x3, I/O: command/status = 0x66, data = 0x62
    Jan 26 12:20:45 further kernel: ACPI: No dock devices found.
    Jan 26 12:20:45 further kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Jan 26 12:20:45 further kernel: \_SB_.PCI0:_OSC request failed
    Jan 26 12:20:45 further kernel: _OSC request data:1 8 1f
    Jan 26 12:20:45 further kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Jan 26 12:20:45 further kernel: PCI host bridge to bus 0000:00
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x03af]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x03b0-0x03df]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x1778-0xffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [mem 0xb0000000-0xffffffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:00.0: [1022:1705] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: [1002:9648] type 00 class 0x030000
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: reg 10: [mem 0xb0000000-0xbfffffff pref]
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: reg 14: [io 0xf000-0xf0ff]
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: reg 18: [mem 0xfeb00000-0xfeb3ffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:00:01.1: [1002:1714] type 00 class 0x040300
    Jan 26 12:20:45 further kernel: pci 0000:00:01.1: reg 10: [mem 0xfeb44000-0xfeb47fff]
    Jan 26 12:20:45 further kernel: pci 0000:00:01.1: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: [1022:1707] type 01 class 0x060400
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: [1022:1709] type 01 class 0x060400
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: [1022:170a] type 01 class 0x060400
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:10.0: [1022:7812] type 00 class 0x0c0330
    Jan 26 12:20:45 further kernel: pci 0000:00:10.0: reg 10: [mem 0xfeb48000-0xfeb49fff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:00:10.0: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: [1022:7801] type 00 class 0x010601
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 10: [io 0xf140-0xf147]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 14: [io 0xf130-0xf133]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 18: [io 0xf120-0xf127]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 1c: [io 0xf110-0xf113]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 20: [io 0xf100-0xf10f]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 24: [mem 0xfeb4d000-0xfeb4d7ff]
    Jan 26 12:20:45 further kernel: pci 0000:00:12.0: [1022:7807] type 00 class 0x0c0310
    Jan 26 12:20:45 further kernel: pci 0000:00:12.0: reg 10: [mem 0xfeb4c000-0xfeb4cfff]
    Jan 26 12:20:45 further kernel: pci 0000:00:12.2: [1022:7808] type 00 class 0x0c0320
    Jan 26 12:20:45 further kernel: pci 0000:00:12.2: reg 10: [mem 0xfeb4b000-0xfeb4b0ff]
    Jan 26 12:20:45 further kernel: pci 0000:00:12.2: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
    Jan 26 12:20:45 further kernel: pci 0000:00:14.0: [1022:780b] type 00 class 0x0c0500
    Jan 26 12:20:45 further kernel: pci 0000:00:14.2: [1022:780d] type 00 class 0x040300
    Jan 26 12:20:45 further kernel: pci 0000:00:14.2: reg 10: [mem 0xfeb40000-0xfeb43fff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:14.3: [1022:780e] type 00 class 0x060100
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: [1022:780f] type 01 class 0x060401
    Jan 26 12:20:45 further kernel: pci 0000:00:14.7: [1022:7806] type 00 class 0x080501
    Jan 26 12:20:45 further kernel: pci 0000:00:14.7: reg 10: [mem 0xfeb4a000-0xfeb4a0ff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:00:18.0: [1022:1700] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.1: [1022:1701] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.2: [1022:1702] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.3: [1022:1703] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.4: [1022:1704] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.5: [1022:1718] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.6: [1022:1716] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.7: [1022:1719] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: [1002:6741] type 00 class 0x030000
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 10: [mem 0xc0000000-0xcfffffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 18: [mem 0xfea20000-0xfea3ffff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 20: [io 0xe000-0xe0ff]
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 30: [mem 0xfea00000-0xfea1ffff pref]
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xfea00000-0xfeafffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: [10ec:8168] type 00 class 0x020000
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: reg 10: [io 0xd000-0xd0ff]
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: reg 18: [mem 0xd0004000-0xd0004fff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: reg 20: [mem 0xd0000000-0xd0003fff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:03:00.0: [168c:002b] type 00 class 0x028000
    Jan 26 12:20:45 further kernel: pci 0000:03:00.0: reg 10: [mem 0xfe900000-0xfe90ffff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:03:00.0: supports D1
    Jan 26 12:20:45 further kernel: pci 0000:03:00.0: PME# supported from D0 D1 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: PCI bridge to [bus 03]
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: bridge window [mem 0xfe900000-0xfe9fffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: PCI bridge to [bus 04] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x0000-0x03af] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x03e0-0x0cf7] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x03b0-0x03df] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x1778-0xffff] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [mem 0xb0000000-0xffffffff] (subtractive decode)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR14._PRT]
    Jan 26 12:20:45 further kernel: \_SB_.PCI0:_OSC request failed
    Jan 26 12:20:45 further kernel: _OSC request data:1 1f 1f
    Jan 26 12:20:45 further kernel: pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    Jan 26 12:20:45 further kernel: pci0000:00: Unable to request _OSC control (_OSC support mask: 0x08)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN24] (IRQs *24)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN25] (IRQs *25)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN26] (IRQs *26)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN27] (IRQs *27)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN28] (IRQs *28)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN29] (IRQs *29)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN30] (IRQs *30)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN31] (IRQs *31)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN32] (IRQs *32)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN33] (IRQs *33)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN34] (IRQs *34)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN35] (IRQs *35)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN36] (IRQs *36)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN37] (IRQs *37)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN38] (IRQs *38)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN39] (IRQs *39)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN40] (IRQs *40)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN41] (IRQs *41)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN42] (IRQs *42)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN43] (IRQs *43)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN44] (IRQs *44)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN45] (IRQs *45)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN46] (IRQs *46)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN47] (IRQs *47)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN48] (IRQs *48)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN49] (IRQs *49)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN50] (IRQs *50)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN51] (IRQs *51)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN52] (IRQs *52)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN53] (IRQs *53)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN54] (IRQs *54)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN55] (IRQs *55)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none
    Jan 26 12:20:45 further kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
    Jan 26 12:20:45 further kernel: vgaarb: loaded
    Jan 26 12:20:45 further kernel: vgaarb: bridge control possible 0000:01:00.0
    Jan 26 12:20:45 further kernel: vgaarb: no bridge control possible 0000:00:01.0
    Jan 26 12:20:45 further kernel: PCI: Using ACPI for IRQ routing
    Jan 26 12:20:45 further kernel: PCI: pci_cache_line_size set to 64 bytes
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8f6c0000-0x8fffffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8f869000-0x8fffffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8fd46000-0x8fffffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8ff00000-0x8fffffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x14f000000-0x14fffffff]
    Jan 26 12:20:45 further kernel: NetLabel: Initializing
    Jan 26 12:20:45 further kernel: NetLabel: domain hash size = 128
    Jan 26 12:20:45 further kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Jan 26 12:20:45 further kernel: NetLabel: unlabeled traffic allowed by default
    Jan 26 12:20:45 further kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    Jan 26 12:20:45 further kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter
    Jan 26 12:20:45 further kernel: Switching to clocksource hpet
    Jan 26 12:20:45 further kernel: pnp: PnP ACPI init
    Jan 26 12:20:45 further kernel: ACPI: bus type pnp registered
    Jan 26 12:20:45 further kernel: pnp 00:00: [bus 00-ff]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x0cf8-0x0cff]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x0000-0x03af window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x03e0-0x0cf7 window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x03b0-0x03df window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x1778-0xffff window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0x000a0000-0x000bffff window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0x000c0000-0x000dffff window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0xb0000000-0xffffffff window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0x00000000 window]
    Jan 26 12:20:45 further kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
    Jan 26 12:20:45 further kernel: pnp 00:01: [mem 0xe0000000-0xefffffff]
    Jan 26 12:20:45 further kernel: system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0010-0x001f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0022-0x003f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0063]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0065]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0067-0x006f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0072-0x007f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0080]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0084-0x0086]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0088]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x008c-0x008e]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0090-0x009f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x00a2-0x00bf]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x00b1]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x00e0-0x00ef]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x04d0-0x04d1]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x040b]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x04d6]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c00-0x0c01]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c14]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c50-0x0c51]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c52]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c6c]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c6f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd0-0x0cd1]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd2-0x0cd3]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd4-0x0cd5]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd6-0x0cd7]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd8-0x0cdf]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0800-0x089f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0000-0xffffffffffffffff disabled]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0000-0x000f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0b20-0x0b3f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0900-0x090f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0910-0x091f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0xfe00-0xfefe]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0060-0x005f disabled]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0064-0x0063 disabled]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfec00000-0xfec00fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfee00000-0xfee00fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfed80000-0xfed8ffff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfed61000-0xfed70fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfec10000-0xfec10fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfed00000-0xfed00fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xff000000-0xffffffff]
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x04d0-0x04d1] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x040b] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x04d6] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c00-0x0c01] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c14] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c50-0x0c51] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c52] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c6c] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c6f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd0-0x0cd1] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd2-0x0cd3] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd4-0x0cd5] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd6-0x0cd7] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd8-0x0cdf] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0800-0x089f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0b20-0x0b3f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0900-0x090f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0910-0x091f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0xfe00-0xfefe] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfec00000-0xfec00fff] could not be reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfee00000-0xfee00fff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfed80000-0xfed8ffff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfed61000-0xfed70fff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfec10000-0xfec10fff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfed00000-0xfed00fff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xff000000-0xffffffff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
    Jan 26 12:20:45 further kernel: pnp 00:03: [dma 4]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0000-0x000f]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0081-0x0083]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0087]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0089-0x008b]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x008f]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x00c0-0x00df]
    Jan 26 12:20:45 further kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0200 (active)
    Jan 26 12:20:45 further kernel: pnp 00:04: [io 0x0070-0x0071]
    Jan 26 12:20:45 further kernel: pnp 00:04: [irq 8]
    Jan 26 12:20:45 further kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
    Jan 26 12:20:45 further kernel: pnp 00:05: [io 0x0061]
    Jan 26 12:20:45 further kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0010-0x001f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0022-0x003f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0044-0x005f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0072-0x007f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0080]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0084-0x0086]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0088]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x008c-0x008e]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0090-0x009f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x00a2-0x00bf]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x00e0-0x00ef]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x04d0-0x04d1]
    Jan 26 12:20:45 further kernel: system 00:06: [io 0x04d0-0x04d1] has been reserved
    Jan 26 12:20:45 further kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
    Jan 26 12:20:45 further kernel: pnp 00:07: [io 0x00f0-0x00ff]
    Jan 26 12:20:45 further kernel: pnp 00:07: [irq 13]
    Jan 26 12:20:45 further kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0c04 (active)
    Jan 26 12:20:45 further kernel: pnp 00:08: [io 0x1770-0x1777]
    Jan 26 12:20:45 further kernel: system 00:08: [io 0x1770-0x1777] has been reserved
    Jan 26 12:20:45 further kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
    Jan 26 12:20:45 further kernel: pnp 00:09: [irq 12]
    Jan 26 12:20:45 further kernel: pnp 00:09: Plug and Play ACPI device, IDs ETD0102 PNP0f13 (active)
    Jan 26 12:20:45 further kernel: pnp 00:0a: [io 0x0060]
    Jan 26 12:20:45 further kernel: pnp 00:0a: [io 0x0064]
    Jan 26 12:20:45 further kernel: pnp 00:0a: [irq 1]
    Jan 26 12:20:45 further kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
    Jan 26 12:20:45 further kernel: pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled]
    Jan 26 12:20:45 further kernel: pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled]
    Jan 26 12:20:45 further kernel: system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
    Jan 26 12:20:45 further kernel: pnp 00:0c: [mem 0xfed00000-0xfed003ff]
    Jan 26 12:20:45 further kernel: pnp 00:0c: Plug and Play ACPI device, IDs PNP0103 (active)
    Jan 26 12:20:45 further kernel: pnp: PnP ACPI: found 13 devices
    Jan 26 12:20:45 further kernel: ACPI: ACPI bus type pnp unregistered
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xfea00000-0xfeafffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: PCI bridge to [bus 03]
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: bridge window [mem 0xfe900000-0xfe9fffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: PCI bridge to [bus 04]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x03af]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 6 [io 0x03b0-0x03df]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 7 [io 0x1778-0xffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 10 [mem 0xb0000000-0xffffffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:01: resource 1 [mem 0xfea00000-0xfeafffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:01: resource 2 [mem 0xc0000000-0xcfffffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci_bus 0000:02: resource 0 [io 0xd000-0xdfff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:02: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci_bus 0000:03: resource 1 [mem 0xfe900000-0xfe9fffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 4 [io 0x0000-0x03af]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 5 [io 0x03e0-0x0cf7]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 6 [io 0x03b0-0x03df]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 7 [io 0x1778-0xffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 8 [mem 0x000a0000-0x000bffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 9 [mem 0x000c0000-0x000dffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 10 [mem 0xb0000000-0xffffffff]
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 2
    Jan 26 12:20:45 further kernel: TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
    Jan 26 12:20:45 further kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    Jan 26 12:20:45 further kernel: TCP: Hash tables configured (established 524288 bind 65536)
    Jan 26 12:20:45 further kernel: TCP: reno registered
    Jan 26 12:20:45 further kernel: UDP hash table entries: 2048 (order: 4, 65536 bytes)
    Jan 26 12:20:45 further kernel: UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 1
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: Boot video device
    Jan 26 12:20:45 further kernel: PCI: CLS 64 bytes, default 64
    Jan 26 12:20:45 further kernel: Unpacking initramfs...
    Jan 26 12:20:45 further kernel: Freeing initrd memory: 2980k freed
    Jan 26 12:20:45 further kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    Jan 26 12:20:45 further kernel: software IO TLB [mem 0x8b6c0000-0x8f6bffff] (64MB) mapped at [ffff88008b6c0000-ffff88008f6bffff]
    Jan 26 12:20:45 further kernel: LVT offset 0 assigned for vector 0x400
    Jan 26 12:20:45 further kernel: perf: AMD IBS detected (0x000000ff)
    Jan 26 12:20:45 further kernel: audit: initializing netlink socket (disabled)
    Jan 26 12:20:45 further kernel: type=2000 audit(1359202838.726:1): initialized
    Jan 26 12:20:45 further kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    Jan 26 12:20:45 further kernel: VFS: Disk quotas dquot_6.5.2
    Jan 26 12:20:45 further kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    Jan 26 12:20:45 further kernel: msgmni has been set to 6857
    Jan 26 12:20:45 further kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Jan 26 12:20:45 further kernel: io scheduler noop registered
    Jan 26 12:20:45 further kernel: io scheduler deadline registered
    Jan 26 12:20:45 further kernel: io scheduler cfq registered (default)
    Jan 26 12:20:45 further kernel: GHES: HEST is not enabled!
    Jan 26 12:20:45 further kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Jan 26 12:20:45 further kernel: Linux agpgart interface v0.103
    Jan 26 12:20:45 further kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
    Jan 26 12:20:45 further kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Jan 26 12:20:45 further kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
    Jan 26 12:20:45 further kernel: mousedev: PS/2 mouse device common for all mice
    Jan 26 12:20:45 further kernel: rtc_cmos 00:04: RTC can wake from S4
    Jan 26 12:20:45 further kernel: rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
    Jan 26 12:20:45 further kernel: rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    Jan 26 12:20:45 further kernel: cpuidle: using governor ladder
    Jan 26 12:20:45 further kernel: cpuidle: using governor menu
    Jan 26 12:20:45 further kernel: drop_monitor: Initializing network drop monitor service
    Jan 26 12:20:45 further kernel: TCP: cubic registered
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 10
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 17
    Jan 26 12:20:45 further kernel: Key type dns_resolver registered
    Jan 26 12:20:45 further kernel: PM: Hibernation image not present or could not be loaded.
    Jan 26 12:20:45 further kernel: registered taskstats version 1
    Jan 26 12:20:45 further kernel: rtc_cmos 00:04: setting system clock to 2013-01-26 12:20:39 UTC (1359202839)
    Jan 26 12:20:45 further kernel: Freeing unused kernel memory: 808k freed
    Jan 26 12:20:45 further kernel: Write protecting the kernel read-only data: 8192k
    Jan 26 12:20:45 further kernel: Freeing unused kernel memory: 1300k freed
    Jan 26 12:20:45 further kernel: Freeing unused kernel memory: 492k freed
    Jan 26 12:20:45 further kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    Jan 26 12:20:45 further systemd-udevd[46]: starting version 197
    Jan 26 12:20:45 further kernel: ACPI: bus type usb registered
    Jan 26 12:20:45 further kernel: usbcore: registered new interface driver usbfs
    Jan 26 12:20:45 further kernel: usbcore: registered new interface driver hub
    Jan 26 12:20:45 further kernel: SCSI subsystem initialized
    Jan 26 12:20:45 further kernel: usbcore: registered new device driver usb
    Jan 26 12:20:45 further kernel: sdhci: Secure Digital Host Controller Interface driver
    Jan 26 12:20:45 further kernel: sdhci: Copyright(c) Pierre Ossman
    Jan 26 12:20:45 further kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: EHCI Host Controller
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: new USB bus registered, assigned bus number 1
    Jan 26 12:20:45 further kernel: QUIRK: Enable AMD PLL fix
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: debug port 1
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: irq 17, io mem 0xfeb4b000
    Jan 26 12:20:45 further kernel: ACPI: bus type scsi registered
    Jan 26 12:20:45 further kernel: libata version 3.00 loaded.
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00
    Jan 26 12:20:45 further kernel: hub 1-0:1.0: USB hub found
    Jan 26 12:20:45 further kernel: hub 1-0:1.0: 5 ports detected
    Jan 26 12:20:45 further kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    Jan 26 12:20:45 further kernel: ohci_hcd 0000:00:12.0: OHCI Host Controller
    Jan 26 12:20:45 further kernel: ohci_hcd 0000:00:12.0: new USB bus registered, assigned bus number 2
    Jan 26 12:20:45 further kernel: ohci_hcd 0000:00:12.0: irq 18, io mem 0xfeb4c000
    Jan 26 12:20:45 further kernel: hub 2-0:1.0: USB hub found
    Jan 26 12:20:45 further kernel: hub 2-0:1.0: 5 ports detected
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: xHCI Host Controller
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 3
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 18, io mem 0xfeb48000
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 40 for MSI/MSI-X
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 41 for MSI/MSI-X
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 42 for MSI/MSI-X
    Jan 26 12:20:45 further kernel: xHCI xhci_add_endpoint called for root hub
    Jan 26 12:20:45 further kernel: xHCI xhci_check_bandwidth called for root hub
    Jan 26 12:20:45 further kernel: hub 3-0:1.0: USB hub found
    Jan 26 12:20:45 further kernel: hub 3-0:1.0: 2 ports detected
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: xHCI Host Controller
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 4
    Jan 26 12:20:45 further kernel: xHCI xhci_add_endpoint called for root hub
    Jan 26 12:20:45 further kernel: xHCI xhci_check_bandwidth called for root hub
    Jan 26 12:20:45 further kernel: hub 4-0:1.0: USB hub found
    Jan 26 12:20:45 further kernel: hub 4-0:1.0: 2 ports detected
    Jan 26 12:20:45 further kernel: sdhci-pci 0000:00:14.7: SDHCI controller found [1022:7806] (rev 0)
    Jan 26 12:20:45 further kernel: Registered led device: mmc0::
    Jan 26 12:20:45 further kernel: mmc0: SDHCI controller on PCI [0000:00:14.7] using ADMA
    Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: version 3.0
    Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: irq 43 for MSI/MSI-X
    Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: AHCI 0001.0300 32 slots 3 ports 3 Gbps 0x7 impl SATA mode
    Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part sxs
    Jan 26 12:20:45 further kernel: scsi0 : ahci
    Jan 26 12:20:45 further kernel: scsi1 : ahci
    Jan 26 12:20:45 further kernel: scsi2 : ahci
    Jan 26 12:20:45 further kernel: ata1: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d100 irq 43
    Jan 26 12:20:45 further kernel: ata2: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d180 irq 43
    Jan 26 12:20:45 further kernel: ata3: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d200 irq 43
    Jan 26 12:20:45 further kernel: usb 1-3: new high-speed USB device number 2 using ehci_hcd
    Jan 26 12:20:45 further kernel: ata3: SATA link down (SStatus 0 SControl 300)
    Jan 26 12:20:45 further kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jan 26 12:20:45 further kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Jan 26 12:20:45 further kernel: ata2.00: ATAPI: MATSHITADVD-RAM UJ8B0, 1.00, max UDMA/100
    Jan 26 12:20:45 further kernel: ata1.00: ATA-8: WDC WD5000BPVT-80HXZT3, 01.01A01, max UDMA/133
    Jan 26 12:20:45 further kernel: ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    Jan 26 12:20:45 further kernel: ata1.00: failed to get Identify Device Data, Emask 0x1
    Jan 26 12:20:45 further kernel: ata2.00: configured for UDMA/100
    Jan 26 12:20:45 further kernel: ata1.00: failed to get Identify Device Data, Emask 0x1
    Jan 26 12:20:45 further kernel: ata1.00: configured for UDMA/133
    Jan 26 12:20:45 further kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD5000BPVT-8 01.0 PQ: 0 ANSI: 5
    Jan 26 12:20:45 further kernel: scsi 1:0:0:0: CD-ROM MATSHITA DVD-RAM UJ8B0 1.00 PQ: 0 ANSI: 5
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Write Protect is off
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Jan 26 12:20:45 further kernel: sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 >
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Attached SCSI disk
    Jan 26 12:20:45 further kernel: sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
    Jan 26 12:20:45 further kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
    Jan 26 12:20:45 further kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
    Jan 26 12:20:45 further kernel: usb 1-5: new high-speed USB device number 4 using ehci_hcd
    Jan 26 12:20:45 further kernel: tsc: Refined TSC clocksource calibration: 1896.550 MHz
    Jan 26 12:20:45 further kernel: Switching to clocksource tsc
    Jan 26 12:20:45 further kernel: Initializing USB Mass Storage driver...
    Jan 26 12:20:45 further kernel: usbcore: registered new interface driver usb-storage
    Jan 26 12:20:45 further kernel: USB Mass Storage support registered.
    Jan 26 12:20:45 further kernel: usb 2-4: new full-speed USB device number 2 using ohci_hcd
    Jan 26 12:20:45 further kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
    Jan 26 12:20:45 further systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
    Jan 26 12:20:45 further systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    Jan 26 12:20:45 further systemd[1]: Set hostname to <further>.
    Jan 26 12:20:45 further systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
    Jan 26 12:20:45 further systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Jan 26 12:20:45 further systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Jan 26 12:20:45 further systemd[1]: Starting Remote File Systems.
    Jan 26 12:20:45 further systemd[1]: Reached target Remote File Systems.
    Jan 26 12:20:45 further systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Jan 26 12:20:45 further systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Jan 26 12:20:45 further systemd[1]: Starting Delayed Shutdown Socket.
    Jan 26 12:20:45 further systemd[1]: Listening on Delayed Shutdown Socket.
    Jan 26 12:20:45 further systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Jan 26 12:20:45 further systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Jan 26 12:20:45 further systemd[1]: Starting udev Kernel Socket.
    Jan 26 12:20:45 further systemd[1]: Listening on udev Kernel Socket.
    Jan 26 12:20:45 further systemd[1]: Starting udev Control Socket.
    Jan 26 12:20:45 further systemd[1]: Listening on udev Control Socket.
    Jan 26 12:20:45 further systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Jan 26 12:20:45 further systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    Jan 26 12:20:45 further systemd[1]: Starting Encrypted Volumes.
    Jan 26 12:20:45 further systemd[1]: Reached target Encrypted Volumes.
    Jan 26 12:20:45 further systemd[1]: Expecting device dev-disk-by\x2duuid-f71c0eee\x2da4ec\x2d43a0\x2d89c7\x2d51f13a79169a.device...
    Jan 26 12:20:45 further systemd[1]: Expecting device dev-disk-by\x2duuid-26f87130\x2d99b7\x2d4a00\x2d997c\x2de177c335f448.device...
    Jan 26 12:20:45 further systemd[1]: Expecting device dev-disk-by\x2duuid-6c6af8e9\x2dbd25\x2d463b\x2dae87\x2dc894d7b092b5.device...
    Jan 26 12:20:45 further systemd[1]: Starting Journal Socket.
    Jan 26 12:20:45 further systemd[1]: Listening on Journal Socket.
    Jan 26 12:20:45 further systemd[1]: Started File System Check on Root Device.
    Jan 26 12:20:45 further systemd[1]: Starting Remount Root and Kernel File Systems...
    Jan 26 12:20:45 further systemd[1]: Starting Load Kernel Modules...
    Jan 26 12:20:45 further systemd[1]: Mounting Huge Pages File System...
    Jan 26 12:20:45 further systemd[1]: Starting udev Coldplug all Devices...
    Jan 26 12:20:45 further systemd[1]: Started Set Up Additional Binary Formats.
    Jan 26 12:20:45 further systemd[1]: Starting Setup Virtual Console...
    Jan 26 12:20:45 further systemd[1]: Mounting POSIX Message Queue File System...
    Jan 26 12:20:45 further systemd[1]: Starting udev Kernel Device Manager...
    Jan 26 12:20:45 further systemd[1]: Starting Apply Kernel Variables...
    Jan 26 12:20:45 further systemd[1]: Mounting Debug File System...
    Jan 26 12:20:45 further systemd[1]: Starting Journal Service...
    Jan 26 12:20:45 further systemd[1]: Started Journal Service.
    Jan 26 12:20:45 further systemd-udevd[142]: starting version 197
    Jan 26 12:20:45 further systemd-journal[145]: Journal started
    Jan 26 12:20:45 further systemd[1]: Started Apply Kernel Variables.
    Jan 26 12:20:45 further systemd[1]: Mounted Debug File System.
    Jan 26 12:20:45 further systemd[1]: Mounted Huge Pages File System.
    Jan 26 12:20:45 further systemd[1]: Started udev Coldplug all Devices.
    Jan 26 12:20:45 further systemd[1]: Mounted POSIX Message Queue File System.
    Jan 26 12:20:45 further systemd[1]: Started udev Kernel Device Manager.
    Jan 26 12:20:45 further kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
    Jan 26 12:20:45 further kernel: ACPI: Power Button [PWRB]
    Jan 26 12:20:45 further kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
    Jan 26 12:20:45 further kernel: ACPI: Sleep Button [SLPB]
    Jan 26 12:20:45 further kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
    Jan 26 12:20:45 further kernel: ACPI: Lid Switch [LID]
    Jan 26 12:20:45 further kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    Jan 26 12:20:45 further kernel: ACPI: Power Button [PWRF]
    Jan 26 12:20:45 further kernel: AMD IOMMUv2 driver by Joerg Roedel <[email protected]>
    Jan 26 12:20:45 further kernel: AMD IOMMUv2 functionality not available on this system
    Jan 26 12:20:45 further kernel: EXT4-fs (sda6): re-mounted. Opts: barrier=0
    Jan 26 12:20:45 further systemd[1]: Started Remount Root and Kernel File Systems.
    Jan 26 12:20:45 further systemd[1]: Starting Local File Systems (Pre).
    Jan 26 12:20:45 further systemd[1]: Reached target Local File Systems (Pre).
    Jan 26 12:20:45 further systemd[1]: Mounting /tmp...
    Jan 26 12:20:45 further systemd[1]: Starting Load Random Seed...
    Jan 26 12:20:45 further systemd[1]: Mounted /tmp.
    Jan 26 12:20:45 further kernel: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
    Jan 26 12:20:45 further kernel: Disabling lock debugging due to kernel taint
    Jan 26 12:20:45 further systemd-modules-load[136]: Inserted module 'fglrx'
    Jan 26 12:20:45 further kernel: <6>[fglrx] Maximum main memory to use for locked dma buffers: 3278 MBytes.
    Jan 26 12:20:45 further kernel: <6>[fglrx] vendor: 1002 device: 9648 count: 1
    Jan 26 12:20:45 further kernel: <6>[fglrx] vendor: 1002 device: 6741 count: 2
    Jan 26 12:20:45 further kernel: <6>[fglrx] ioport: bar 1, base 0xf000, size: 0x100
    Jan 26 12:20:45 further kernel: <6>[fglrx] ioport: bar 4, base 0xe000, size: 0x100
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: enabling device (0000 -> 0003)
    Jan 26 12:20:45 further kernel: <6>[fglrx] Kernel PAT support is enabled
    Jan 26 12:20:45 further kernel: <6>[fglrx] module loaded - fglrx 9.1.11 [Dec 19 2012] with 2 minors
    Jan 26 12:20:45 further systemd[1]: Started Load Kernel Modules.
    Jan 26 12:20:45 further systemd[1]: Mounted FUSE Control File System.
    Jan 26 12:20:45 further systemd[1]: Mounted Configuration File System.
    Jan 26 12:20:45 further systemd[1]: Started Load Random Seed.
    Jan 26 12:20:45 further

    During boot there is a problem with your fglrx driver. It tries to use MSI interrupts instead of old pin-based method, but it is allready enabled and it warns you http://lxr.linux.no/linux+v3.7.4/drivers/pci/msi.c#L811 in line 828
    And during shutdown there is a problem with pci_msi_shutdown. Maybe this problems related with each other?
    try to disable globaly msi by adding nomsi to kernel options. If this help try to disable msi just for catalyst after boot by echo 0 in /sys/bus/pci/devices/[faulty device]/msi_bus
    try to raise debug level to see message dev_dbg(dev, "shutdown\n"); here http://lxr.linux.no/linux+v3.7.4/drivers/base/core.c#L , open an entry in bugzilla
    try do upgrade or downgrade catalyst if possible
    switch to open source driver

  • Problems with Comodo Kill Switch, Windows Services & Bitlocker Encryption on Asus N56VZ

    Hi All,
    So recently I found myself stuck in a different scenario than before, and after many hours researching and efforts to fix this I still find myself stuck  yet with a few options still to fix.
    What is the problem?
    So as a security cautious user when i first got to Windows 8.1 Pro 64Bit I encrypted both the C and D drive (Split the main disk) to protect myself and my family. Unfortunately that has not been very helpful with the way in which booting and running from
    either external USB devices or CD/DVD works, not allowing myself to at all.
    My usual security suit I  use is Comodo Internet Security, which additionally comes with Comodo Kill Switch. Whilst using the application instead of stopping one of the TCP connections I was meant to I accidently stopped an Windows Explorer connection.
    For some reason since then Windows Explorer, nor most windows apps or services themselves will run. For example msconfig will run but sfc /scannow or mmc will not, whether in safe mode or normal mode.
    What Caused the Problem?
    Cannot 100% say
    What I Think Caused the Problem?
    Myself running Comodo Kill Switch stopping a vital server connection with Windows Explorer that messed up alot. Or a potential Virus unknown how cannot fully scan system as wont boot externally or run many apps.
    Additional Info
    Asus Webcam is Disabled on Purpose
    Laptop was fully customized to run latest games full graphics minus Anti Aliasing, works with Evolve + CoD Advanced Warfare
    Laptop does not boot if USB Keyboard plugged in, works with everything else normal (had this on other systems no problem for me)
    Ask me for more info if required to add here, braindead again
    Specifications of my system
    Intel® Core™ i7 3610QM Processor
    Windows 8.1 Pro 64Bit
    Intel® HM76 Chipset
    DDR3 1600 MHz SDRAM, 2 x SO-DIMM 8GB
    15.6" HD (1366x768)/Full HD (1920x1080)/Wide View Angle LED Backlight
    NVIDIA® GeForce® GT 650M with 2GB DDR3 VRAM
    1TB 5400RPM OR 750GB 5400/7200RPM (Cannot remember off top of head, braindead)
    Super-Multi DVD 
    Kensington lock (Security Feature)
    LoJack (Security Feature)
    BIOS Booting User Password Protection (Security Feature)
    HDD User Password Protection and Security (Security Feature)
    Pre-OS Authentication by programmable key code (Security Feature)
    What Can Run and Won't Run?
    ON BOOT:
    Bitlocker Encryption Password & Advanced Settings are accessible
    Bios (password protected) is accessible
    Windows Recovery Mode is accessible (Think it is F9 or F10)
    Windows Logon Password Screen is accessible
    ON NORMAL/SAFE-MODE START UP:
    After Log-In Windows Explorer will not run
    Task Manager will run, also allows me to browse the files when trying to start new task
    Can run Command prompt
    Cannot run any control panel items
    Cannot run services.msc
    Cannot run mmc
    Cannot run sfc
    Every time it metions windows drive is locked
    Start Error's when running certain applications (Will post codes soon)
    Rufus USB Tool does run
    Cannot boot Kali Linux off USB
    Cannot boot Windows 8.1 off USB
    Cannot boot Windows 8.1 off DVDRW
    Fixwin2 will not run
    Apps either work or don't whether in safe mode or normal
    Cannot use Windows Installer
    What Fixes I Have Tried So Far
    Ok so like any normal user I don't want to lose my files. So here are what I have tried so far:
    Repair MBR (Repair Completed, No Luck)
    SFC /SCANNOW (Returns Error 'Windows Resource Protection could not start the repair service')
    Tried sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows (Could not access drive)
    Fixwin2 (Will not run in either normal or safe mode)
    Booting using Windows 8.1 via USB (Cannot boot from extermal devices due to Bitlocker Encryption)
    Booting using Kali Linux Via DVD & USB (Cannot boot from external devices due to Bitlocker Encrytption)
    How do I know it is because of Bitlocker, because last time I disabled it, I could run from external devices
    Tried to run bitlocker to change settings (Will not run)
    Have used both password and recovery keys to unlock driver, they work but when applications are running on windows the drive is still locked?
    Tried windows Automatic Diagnostic and Repair (Could not repair anything, did make a log I am still to extract from the syste)
    There are No System Restore Points
    I'm sure there is much more information I could post however I will leave it on an ask to know basis, apart from the log files and further information to gather. Below is my list of trial and error fixes to try for today (need more ideas and help please!):
    Hiren's 15.2 Boot CD via DVD (NOT ABLE TO BOOT)
    Hiren's 15.2 Boot CD via USB (NOT ABLE TO BOOT)
    Research into the Bios and Possible Update in-case of implementation of Virus, can access flash utility (STILL NOT TESTED)
    Try and get a portable version or a working version of windows installer to try and re-install Comodo Internet Security (STILL NOT TESTED)
    Another way to disable Bitlocker
    Anti-Malware / Anti-Virus Scan If Possible to Run One
    Bitlocker Repair Tool, will try this also
    I have posted this as have not found much info online, usually find it and crack on but this time things are a little more tricky, my priority task I really need to do is remove the Bitlocker Encryption, but if the application will not run... what do I do
    then?
    Thanks for your time reading all, Sorry for any poor formatting or spelling.
    Update 1: MMC.exe Error Code
    Ok so now have the computer in safe mode, still same as before, no explorer.exe, no services etc... Just went into the Task Manager > Services (Tab) > Open Services (Option at bottom)
    This is the error I get:
    'The Instruction at 0x785a746c referenced memory at 0x000000a8. The memory could not be read.
    Any Ideas on what this error is and why?
    Update 2: CHKDSK Works with no Fix
    Update 3: Hiren's 15.2 Boot CD - USB Boot still no luck booting around Bitlocker Encryption
    Just to explain again, I already have unlocked the drive with correct bitlocker password or recovery key yet the drive remains locked not allowing windows refresh of files of complete install from the windows recovery menu as keeps saying drive is locked

    Ok so attempt number two to write this update via bloody phone! (Just refreshed page whilst writing!)
    Update 4:
    Problem - cannot run from bootable devices (DVD/USB)
    Cause - bitlocker fully encrypted drive stops this working
    Repair - Boot up holding F9 to enter windows recovery Input Bitlocker recovery keys to unlock drives
    Navigate to Command Prompt in advanced settings Execute following code:
    Repair-bde c: d: -rp 000111-222333-444555-etc...
    (Code found from https://technet.microsoft.com/en-us/library/ee523219%28v=ws.10%29.aspx)
    Note for those using this: It is common while unlocking certain drives to get errors such as: Quote from http://www.benjaminathawes.com/2013/03/17/resolving-partial-encryption-problems-with-bitlocker/
    "LOG INFO: 0x0000002aValid metadata at offset 8832512000 found at scan level
    1.LOG INFO: 0x0000002b Successfully created repair context.
    LOG ERROR: 0xc0000037 Failed to read sector at offset 9211592704.
    (0×00000017) LOG ERROR: 0xc0000037 Failed to read sector at offset 9211593216.
    (0×00000017) …followed by around 20 similar entries that differed only by the offset value"
    Repair Status for Update 4: COMPLETED - However over wrote D drive data so now need to recover that
    Problem 2 - windows services corrupted along with windows files
    Cause - Unknown
    Repair - wait until system is fully decrypted Once fully decrypted ensure boot from USB/DVD
    Re-do fixes that would not work before if this has fixed boot issue Confirm fix / update post Hope anything I put here helps others also

  • How to kill Active Data Request in DSO

    Hi all,
    I have 2 dsos ( A, B). Data loads from A to B.
    Now I have deleted data from DSO B by using option delete data ( did killed one running request by turing the status to RED).
    when I try to load data again to DSO B, it is not allowing me to execute the DTP.
    Message is Request 257.617 is stil processing.
    I am SAP BI 7.0 environment.
    Please suggest how to kill active request ( I am not seeing it RSMO/SM37).
    I tried to use Zombie Request FM, it didnt worked.
    Thanks All,
    Jason

    Srinivas,
    Thanks for the reply.
    When I go RSRQ
    I can see the request , the exception it is showing is CX_RS_FAILED logged.
    SM51, when try to kill the process it says
    SAP System Message:
    Work Process restarted; session terminated
    Apologies for earlier post messages saying that I did nt saw the message in RSMO, I can see it is in yellow process.
    Please suggest how to kill the processes .
    Apperciate your response..
    Thank you
    Jason

  • New Prob. iTunes kills browser functionality. Have to reboot sat. modem.

    When I start iTunes, my browser functionality is killed in both Firefox and IE. Pages start to load and then say, 'done'. Blank browser screen. Email and IM still function normally. I have to close browsers and then reboot my satellite modem before browser function returns. Any clues? I love iTunes and have committed my entire library to it, but I'm at my wits end. Life without music? Thanks.
    Dell something   Windows XP Pro  

    Turn off the sharing functionality (both the "look for shared music" as well as the "share my music") and the functionality that lets it look for and find remote speakers. That will most likely prevent it from freezing your satellite modem when you start iTunes.
    Also, look into a software or firmware upgrade for your satellite modem, since it obviously has some kind of bug internally as well.

  • Plugging official DVI to Video adaptor to Macbook Pro 3,1 recently updated to Mavericks killed my Macbook's SMC

    So it happens that since Lion and now, of course, Mavericks, the DVI to Video/S-Video support is not only unsupported, but crashes your 2008 Macbook Pro (MacbookPro3,1, 15 inch) if you plug the official adaptor in. The screen went with artifacts and the computer needed a hard reset.
    What happened after that is that the computer wouldn't start. Of course I immediately did SMC and PRAM resets without results. No leds, no start chime, nothing. Only method found was to bypass the SMC (which is done via holding de power button with battery/power cord unplugged, then plugging power cord still holding it, releasing, and pressing it again). Everything is then ok except, of course, everything controlled by the SMC (no battery, leds, fans at full speed). Did Apple's Hardware Check, full test, no errors found. Reflashed manually the SMC via an EFI Shell, as found on the internet: the SMC is in "U" mode and can't be correctly reflashed. After that, I unmounted the logic board looking for any kind of corruption; found nothing.
    In resume, did everything I could for a week. The last thing I found out is that plugging the adaptor itself, without connecting to any external device (no TV), still crashes the screen with artifacts. I beleive this has to do with the adaptor having inside some chips, since it's function is not to rewire cables, but to convert one signal to another. What happens after that and a hard-reset again, and after that hard reset the now installed rEFIt screen doesn't appear, so I believe that, effectively, connecting the adaptor affects your computer's boot system somehow.
    I know Apple doesn't support computers old as these anymore, and I don't even care they quit the Video-out support with their new free OS, but if by doing that you enable your own official 20-30€ adaptor to kill an otherwise fully functional Macbook, that's foul play.
    Any advice will be greatly received. Thanks for reading.

    Forgot to mention that the DVI adaptor works ok if plugged to a DVI monitor, so it's not a physical problem from the DVI output plug.

  • I mistakenly asked iTunes to download a TV series and I can't get it to stop trying to download it.   how do I kill the download?

    I mistakenly asked iTunes to download a TV series and I can't get it to stop trying to download it.   how do I kill the download?

    You've got to be freakin' kidding me. I'm in Brazil, I accidentally started a 2.2GB download that it says will take 592 minutes to download, and there's no way I can stop it and download something else until that first download finishes? I would have thought it was unthinkable 15 years ago that anyone would build an app that downloads things but doesn't allow the option of canceling the download, but in this day and age? So much for Apple making intuitive, user-friendly products.

  • Why it is taking too much time to kill the process?

    Hi All,
    Today,one of my user ran the calc script and the process is taking too much time, then i kill the process. I am wondering about one thing here even it is taking too long to kill the process, generally it will not take more than 2 sec. I did this through EAS.
    After that I ran Maxl statement
    alter system kill request 552599515;
    there is no use at all.
    Please reply if you have any solutions to kill this process.
    Thanks in advance.
    Ram.

    Hi Ram,
    1. Firstly, How much time does your calculation scripts normally run.
    2. While it was running, you can go to the logs and monitor where exactly the script is taking time .
    3. Sometimes, it does take time to cancel a transaction ( as it might be in between).
    4. Maxl is always good to kill ,as you did . It should be succesful . Check the logs what it says ,and also the "sessions" which might say "terminating" and finish it off.
    5. If nothing works ,and in the worst case scenarion , if its taking time without doing anything. Then log off all the users and stop the databas and start it .
    6. Do log off all the users, so that you dont corrupt any filter related sec file.
    Be very careful , if its production ( and I assume you have latest backups)
    Sandeep Reddy Enti
    HCC
    http://hyperionconsultancy.com/

  • Mac killing off my songs.. one by one, showing the (!) exclamation point

    I got my macbook pro in July, and everything has worked fine. The only problems I've had are with my itunes. I transfered all my music from my old computer onto my new itunes and onto my new ipod, and it all went fine. Then a week or two later I tried to listen to a certain artist, and half the songs were missing. As I clicked to play them, the exclamation point would pop up. So I followed the window and went looking through my files to revive them, but they were nowhere to be found. I searched my whole hard drive for them, and they were no where. I then realized that this was happening with other artists too. A song here or there, and then whole albums would have that . My computer simply erased them. They were even still on my ipod. Luckily I still have all the files on my old desktop so I recopied them, and figured it would be fine.
    Not really.
    After I fixed those songs, my computer just erased a few MORE. Just random songs. They'd just be gone from my computer. Poofed out of thin air! I moved away and can't go retrieve them from my old computer, and I refuse to have to always do that. My computer should not be doing this. Slowly, one by one, another song will go missing, one by one. Now, it has started happening to my purchased items! Ones that I just bought a few weeks ago! Disappeared! Sitting there with that stupid in the "purchased" playlist!
    I'm really sick of it and would like some answers. How can I retrieve these? I heard there's a form on the site to state a claim so they will allow you to redownload your purchased items, or send them to you or something, but I couldn't find it. And I'd really just like itunes to stop killing my files.
    Please help!!

    try if this script helps:
    _*iTunes Track CPR v1.3*_
    This script attempts to locate the files of so-called "dead tracks"--iTunes tracks designated with (!)--that you assume are not actually missing but are still located in the iTunes Music folder in their "iTunes File Order" (Music -> Artist -> Album -> file.xxx)."
    also useful:
    _*Music Folder Files Not Added v2.0*_
    This application will list the file paths of the files in your designated "iTunes Media" folder which are not in iTunes' library. Additionally, you can select a different parent folder and its contents will be compared to the iTunes library. Options to Add a selection of found files to iTunes or move them to the Trash.
    JGG

  • Multiple instances of firefox running cannot kill in task manager "Access denied"

    There's no issue with starting a new instance after closing one, the "firefox is already running" error is not occurring (ok maybe once or twice a month, but it's not related to this problem, as my problem happens all the time.)
    Apparently when closing a ff window it never fully stops. My computer slows down because of it and these multiple instances of firefox show up in Task Manager. When I try to kill the extra processes it just goes "BANG" and the "access denied" error dialog box appears. They are all running under my user account, and in CPU some are just 10 or 25 and some are in the hundreds and some are over a million. what the heck is going on?
    I'm running Windows 7 64 bit and ff 23.0 but this has been happening since about ff 15 (?)

    When closing Firefox completely, it is important to close it using the <i>Exit</i> button, located inside of the Firefox/File menu.
    Another cause to this problem could be a Firefox preloader. Do you have any programs that will load Firefox automatically? They are supposed to improve start time.
    You can also '''try Firefox Safe Mode''' to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.
    ''(If you're not using it, switch to the Default theme.)''
    * Open the Help menu and click on the '''Restart with Add-ons Disabled...''' menu item while Firefox is running.
    ''Once you get the pop-up, just select "'Start in Safe Mode"''
    '''''If the issue is not present in Firefox Safe Mode''''', your problem is probably caused by an extension, and you need to figure out which one. Please follow the [[Troubleshooting extensions and themes]] article for that.
    ''To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.''
    I hope that one of my solutions helps to fix your problem. Please report back with updates soon.
    <b>NOTE: </b>You are using an outdated version of Firefox. This can cause security and functionality issue. Please update to the most recent version as soon as possible.

Maybe you are looking for

  • Drag and Drop interaction.

    I really struggle with setting this up. The Finish button stays inactive. Is the a tutorial for this? Kindly, Jake

  • User not found in AD

    Hi Fella and all, I've finally complete my wlc setup with IAS as radius server. The setup for one of the user wlan is layer 3 authentication without any layer 2 security.I encounter a problem while authenticating thru web. below is the debug msg from

  • Screen view distorted on initial boot up

    Once I set screen preferemces (1920x1080) on my initial startup of Lion, the gray apple (or boot drive choices with opt. startup) have been in the proper configuration without distortion, Today, I created my own Lion Thumb Drive and when I tested by

  • Looping through a cursor (newbie)

    I am trying to construct a dynamic insert statement. I am retrieving (using a select) the column names from one of my tables into a cursor. I would now like to loop through the cursor and extract the column names. Is there anyway to loop through the

  • OSB maintenance scripts

    Where can I find more information about OSB's maintenance scripts?  Specifically, what is responsible for rotation and cleanup of old files under /usr/local/oracle/backup/admin/history/host/ on the OSB server? I have files under /usr/local/oracle/bac