[SOLVED] K Display Manager won't start up at boot
EDIT: I'm retarded. I hadn't even checked to see xorg-server was installed. It wasn't.
Hi,
I just installed package group kde-meta for a full KDE installation including KDM, installed xf86-video-ati for video card drivers, and then ran:
systemctl enable kdm.service
systemctl disable getty@tty1
Now, when I start up, I just get the messages "Starting K Display Manager..." and "Started K Display Manager." but the X server doesn't start up at all. Those messages are left on the screen. Using 'systemctl start kdm.service' does nothing. Literally no output or anything.
What should I do? Also, I know there's not much information, but if you give me some commands I can get some logs. I just don't know where to look for them...
Thanks in advance.
Last edited by Archimaredes (2013-01-25 19:06:33)
I've just been experiencing a similar issue. The local Apple Store just replaced my logic board (was overheating without secondary cooling when processor was under a full load, and the fans weren't kicking) for a little more trivial problem. Now that I just got it back, it ran for about 5 minutes before it spontaneously shutdown. I started it back immediately after that, and it went for only another couple minutes before it gave up yet again. After that, it just plain old wouldn't boot. Tried to reset the PRAM...wouldn't even get that far. Tried to reset the PMU...saw no change.
Whenever I try to boot it, I can hear the fan on the left start up and the hard drive attempt to spin up. Shortly after, it makes a subtle chirp-like noise and promptly shuts off. Mind you, I'm getting no display or anything 'cept these noises. I'm trying to get it to the point that I can run the diagnostics program from the OS X disc, but I think I'm going to be lucky to even get that far.
I'm thinking twice before taking my MacBook Pro to get serviced for something that isn't work-impairing now!
Similar Messages
-
Password Manager won't start. If I click on the ThinkVantage icon and go to Security, Protection, and Recovery > Manage passwords, it makes the system tray icon show up but it doesn't fill in passwords. If I right click on the system tray icon and click Open Password Manager... it doesn't do anything.
Any ideas?jpd111 wrote:
I loaded them up, rebooted and everything is fine now.
Welcome to the forum, jpd111, and congratulations on being our 20,000th new member!
And thanks to Justin for sharing his knowledge and experience with others!
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Jane
2015 X1 Carbon, ThinkPad Slate, T410s, X301, X200 Tablet, T60p, HP TouchPad, iPad Air 2, iPhone 5S, IdeaTab A2107A, Yoga Tablet, Yoga 3 Pro
I am not a Lenovo Employee.
I AM one of those crazy ThinkPad zealots!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! -
I upgraded to 3.1(2a) and then I reinstalled Fabric Manger and Device Manager. Fabric Manager won't start, error is "Unable to connect to server! Admin login from 127.0.0.1 failed". Device Manager is fine.
I am running into the same situation but with FM(3.0.2a) on a Windows Server 2003. We are using Citrix for FM client login. Looking at the windows services FM server services is in running status. The second login attempt would work, not sure why?
When log in locally via windows remote desktop connection we get these error dialogs "ERROR Open Fabric - Fabric Manager 3.0(2a) Error in register for events: Connection refused to host: 10.1.x.x;nested exception is:java.net.ConnectException: Connection timed out: connect
and
NoSuchOject: no such object in table
After clear these dialogs the second attempt with work.
I can see login issues from remote client but even locally on the server? Any suggestions?
Thanks, -
My Mac book pro won't start! It boots as far as the sign in screen and then everything goes black. Please help.
Which model MacBook Pro do you have (e.g., “15-inch Late 2011”) and which version of OS X are you running?
Clinton -
[Solved] Graphical display won't start from cold boot.
I noticed that if I turn on my computer and boot into linux the screen will go black after trying to start the display manager. Rebooting into linux will again display a blank black screen. Switching to TTY's with ctrl-alt-F* doesn't appear to work. If I boot into windows then boot linux the display works.
I haven't been able to debug much because I can only cause this bug to occur after letting the computer sit off for a while. Shutting the computer down (systemctl poweroff) doesn't cause it, leaving it unplugged for a minute didn't cause it either.
Today I tested ways to recreate the error without waiting, I don't remember how many things I tried, so I can't include boot logs from a failed boot, I'll grab them next time the bug happens.
I'm running linux-ck and nvidia drivers installed from the linux-ck unofficial repository mentioned in the linux-ck wiki page.
- Kernel: repo-ck/linux-ck-ivybridge 3.12.9-3
- Graphics: repo-ck/nvidia-ck-ivybridge 331.38-2
- Display manager: community/lightdm 1:1.8.6-1
Hardware:
- ASRock Z77 Extreme4 ATX LGA1155 Motherboard
- GTX 670 Graphics card.
Solution:
This was an issue with windows 8.1 fast start up, which is enabled by default. Instead of performing a clean shutdown windows will hibernate to disk. When linux booted the disks failed to mount.
I disabled fast startup in windows Control Panel > Power Options > System Settings.
Last edited by seniorsassycat (2014-02-07 18:56:44)So I left my computer off for more than three hours and the display started fine when I turned the computer on. This morning after the computer was off for about eight hours the display wouldn't come on. I have boot logs from a good, and a bad boot.
Failed Boot
-- Logs begin at Sun 2013-05-19 13:01:58 EDT, end at Fri 2014-02-07 11:57:16 EST. --
Feb 07 11:54:25 ragnarok systemd-journal[130]: Runtime journal is using 1.3M (max 393.6M, leaving 590.4M of free 3.8G, current limit 393.6M).
Feb 07 11:54:25 ragnarok systemd-journal[130]: Runtime journal is using 1.3M (max 393.6M, leaving 590.4M of free 3.8G, current limit 393.6M).
Feb 07 11:54:25 ragnarok kernel: Initializing cgroup subsys cpuset
Feb 07 11:54:25 ragnarok kernel: Linux version 3.12.9-3-ck (squishy@ease) (gcc version 4.8.2 20131219 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Feb 2 14:51:38 EST 2014
Feb 07 11:54:25 ragnarok kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-ck root=UUID=b5bc95f0-b132-4697-b135-7f972efcbf65 rw elevator=bfq resume=/dev/sdb1 init=/usr/lib/systemd/systemd
Feb 07 11:54:25 ragnarok kernel: e820: BIOS-provided physical RAM map:
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x0000000040005000-0x00000000c98c1fff] usable
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000c98c2000-0x00000000c9f4cfff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000c9f4d000-0x00000000ca1ccfff] ACPI NVS
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000ca1cd000-0x00000000ca1d1fff] ACPI data
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000ca1d2000-0x00000000ca214fff] ACPI NVS
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000ca215000-0x00000000cac0afff] usable
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000cac0b000-0x00000000caff1fff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000caff2000-0x00000000caffffff] usable
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000cb800000-0x00000000cf9fffff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 07 11:54:25 ragnarok kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f5fffff] usable
Feb 07 11:54:25 ragnarok kernel: NX (Execute Disable) protection: active
Feb 07 11:54:25 ragnarok kernel: SMBIOS 2.7 present.
Feb 07 11:54:25 ragnarok kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Extreme4, BIOS P1.20 03/08/2012
Feb 07 11:54:25 ragnarok kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 07 11:54:25 ragnarok kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 07 11:54:25 ragnarok kernel: No AGP bridge found
Feb 07 11:54:25 ragnarok kernel: e820: last_pfn = 0x22f600 max_arch_pfn = 0x400000000
Feb 07 11:54:25 ragnarok kernel: MTRR default type: uncachable
Feb 07 11:54:25 ragnarok kernel: MTRR fixed ranges enabled:
Feb 07 11:54:25 ragnarok kernel: 00000-9FFFF write-back
Feb 07 11:54:25 ragnarok kernel: A0000-BFFFF uncachable
Feb 07 11:54:25 ragnarok kernel: C0000-CFFFF write-protect
Feb 07 11:54:25 ragnarok kernel: D0000-EBFFF uncachable
Feb 07 11:54:25 ragnarok kernel: EC000-FFFFF write-protect
Feb 07 11:54:25 ragnarok kernel: MTRR variable ranges enabled:
Feb 07 11:54:25 ragnarok kernel: 0 base 000000000 mask E00000000 write-back
Feb 07 11:54:25 ragnarok kernel: 1 base 200000000 mask FE0000000 write-back
Feb 07 11:54:25 ragnarok kernel: 2 base 220000000 mask FF0000000 write-back
Feb 07 11:54:25 ragnarok kernel: 3 base 0E0000000 mask FE0000000 uncachable
Feb 07 11:54:25 ragnarok kernel: 4 base 0D0000000 mask FF0000000 uncachable
Feb 07 11:54:25 ragnarok kernel: 5 base 0CC000000 mask FFC000000 uncachable
Feb 07 11:54:25 ragnarok kernel: 6 base 0CB800000 mask FFF800000 uncachable
Feb 07 11:54:25 ragnarok kernel: 7 base 22F800000 mask FFF800000 uncachable
Feb 07 11:54:25 ragnarok kernel: 8 base 22F600000 mask FFFE00000 uncachable
Feb 07 11:54:25 ragnarok kernel: 9 disabled
Feb 07 11:54:25 ragnarok kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Feb 07 11:54:25 ragnarok kernel: e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
Feb 07 11:54:25 ragnarok kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
Feb 07 11:54:25 ragnarok kernel: found SMP MP-table at [mem 0x000fcd40-0x000fcd4f] mapped at [ffff8800000fcd40]
Feb 07 11:54:25 ragnarok kernel: Scanning 1 areas for low memory corruption
Feb 07 11:54:25 ragnarok kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 07 11:54:25 ragnarok kernel: [mem 0x00000000-0x000fffff] page 4k
Feb 07 11:54:25 ragnarok kernel: BRK [0x01b11000, 0x01b11fff] PGTABLE
Feb 07 11:54:25 ragnarok kernel: BRK [0x01b12000, 0x01b12fff] PGTABLE
Feb 07 11:54:25 ragnarok kernel: BRK [0x01b13000, 0x01b13fff] PGTABLE
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0x22f400000-0x22f5fffff]
Feb 07 11:54:25 ragnarok kernel: [mem 0x22f400000-0x22f5fffff] page 2M
Feb 07 11:54:25 ragnarok kernel: BRK [0x01b14000, 0x01b14fff] PGTABLE
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0x22c000000-0x22f3fffff]
Feb 07 11:54:25 ragnarok kernel: [mem 0x22c000000-0x22f3fffff] page 2M
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0x200000000-0x22bffffff]
Feb 07 11:54:25 ragnarok kernel: [mem 0x200000000-0x22bffffff] page 2M
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 07 11:54:25 ragnarok kernel: [mem 0x00100000-0x001fffff] page 4k
Feb 07 11:54:25 ragnarok kernel: [mem 0x00200000-0x1fffffff] page 2M
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0x20200000-0x40003fff]
Feb 07 11:54:25 ragnarok kernel: [mem 0x20200000-0x3fffffff] page 2M
Feb 07 11:54:25 ragnarok kernel: [mem 0x40000000-0x40003fff] page 4k
Feb 07 11:54:25 ragnarok kernel: BRK [0x01b15000, 0x01b15fff] PGTABLE
Feb 07 11:54:25 ragnarok kernel: BRK [0x01b16000, 0x01b16fff] PGTABLE
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0x40005000-0xc98c1fff]
Feb 07 11:54:25 ragnarok kernel: [mem 0x40005000-0x401fffff] page 4k
Feb 07 11:54:25 ragnarok kernel: [mem 0x40200000-0xc97fffff] page 2M
Feb 07 11:54:25 ragnarok kernel: [mem 0xc9800000-0xc98c1fff] page 4k
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0xca215000-0xcac0afff]
Feb 07 11:54:25 ragnarok kernel: [mem 0xca215000-0xca3fffff] page 4k
Feb 07 11:54:25 ragnarok kernel: [mem 0xca400000-0xcabfffff] page 2M
Feb 07 11:54:25 ragnarok kernel: [mem 0xcac00000-0xcac0afff] page 4k
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0xcaff2000-0xcaffffff]
Feb 07 11:54:25 ragnarok kernel: [mem 0xcaff2000-0xcaffffff] page 4k
Feb 07 11:54:25 ragnarok kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
Feb 07 11:54:25 ragnarok kernel: [mem 0x100000000-0x1ffffffff] page 2M
Feb 07 11:54:25 ragnarok kernel: RAMDISK: [mem 0x379f8000-0x37cf3fff]
Feb 07 11:54:25 ragnarok kernel: ACPI: RSDP 00000000000f0450 00024 (v02 ALASKA)
Feb 07 11:54:25 ragnarok kernel: ACPI: XSDT 00000000ca1b4078 00074 (v01 ALASKA A M I 01072009 AMI 00010013)
Feb 07 11:54:25 ragnarok kernel: ACPI: FACP 00000000ca1bdb80 000F4 (v04 ALASKA A M I 01072009 AMI 00010013)
Feb 07 11:54:25 ragnarok kernel: ACPI: DSDT 00000000ca1b4188 099F2 (v02 ALASKA A M I 00000014 INTL 20051117)
Feb 07 11:54:25 ragnarok kernel: ACPI: FACS 00000000ca1cbf80 00040
Feb 07 11:54:25 ragnarok kernel: ACPI: APIC 00000000ca1bdc78 00072 (v03 ALASKA A M I 01072009 AMI 00010013)
Feb 07 11:54:25 ragnarok kernel: ACPI: ASF! 00000000ca1bdcf0 000A5 (v32 INTEL HCG 00000001 TFSM 000F4240)
Feb 07 11:54:25 ragnarok kernel: ACPI: MCFG 00000000ca1bdd98 0003C (v01 ALASKA A M I 01072009 MSFT 00000097)
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT 00000000ca1bddd8 004A6 (v01 Intel_ AoacTabl 00001000 INTL 20091112)
Feb 07 11:54:25 ragnarok kernel: ACPI: AAFT 00000000ca1be280 000C2 (v01 ALASKA OEMAAFT 01072009 MSFT 00000097)
Feb 07 11:54:25 ragnarok kernel: ACPI: HPET 00000000ca1be348 00038 (v01 ALASKA A M I 01072009 AMI. 00000005)
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT 00000000ca1be380 0036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT 00000000ca1be6f0 009AA (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT 00000000ca1bf0a0 00A92 (v01 PmRef CpuPm 00003000 INTL 20051117)
Feb 07 11:54:25 ragnarok kernel: ACPI: Local APIC address 0xfee00000
Feb 07 11:54:25 ragnarok kernel: [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226c00000-ffff88022ebfffff] on node 0
Feb 07 11:54:25 ragnarok kernel: Zone ranges:
Feb 07 11:54:25 ragnarok kernel: DMA [mem 0x00001000-0x00ffffff]
Feb 07 11:54:25 ragnarok kernel: DMA32 [mem 0x01000000-0xffffffff]
Feb 07 11:54:25 ragnarok kernel: Normal [mem 0x100000000-0x22f5fffff]
Feb 07 11:54:25 ragnarok kernel: Movable zone start for each node
Feb 07 11:54:25 ragnarok kernel: Early memory node ranges
Feb 07 11:54:25 ragnarok kernel: node 0: [mem 0x00001000-0x0009cfff]
Feb 07 11:54:25 ragnarok kernel: node 0: [mem 0x00100000-0x1fffffff]
Feb 07 11:54:25 ragnarok kernel: node 0: [mem 0x20200000-0x40003fff]
Feb 07 11:54:25 ragnarok kernel: node 0: [mem 0x40005000-0xc98c1fff]
Feb 07 11:54:25 ragnarok kernel: node 0: [mem 0xca215000-0xcac0afff]
Feb 07 11:54:25 ragnarok kernel: node 0: [mem 0xcaff2000-0xcaffffff]
Feb 07 11:54:25 ragnarok kernel: node 0: [mem 0x100000000-0x22f5fffff]
Feb 07 11:54:25 ragnarok kernel: On node 0 totalpages: 2070113
Feb 07 11:54:25 ragnarok kernel: DMA zone: 64 pages used for memmap
Feb 07 11:54:25 ragnarok kernel: DMA zone: 21 pages reserved
Feb 07 11:54:25 ragnarok kernel: DMA zone: 3996 pages, LIFO batch:0
Feb 07 11:54:25 ragnarok kernel: DMA32 zone: 12868 pages used for memmap
Feb 07 11:54:25 ragnarok kernel: DMA32 zone: 823493 pages, LIFO batch:31
Feb 07 11:54:25 ragnarok kernel: Normal zone: 19416 pages used for memmap
Feb 07 11:54:25 ragnarok kernel: Normal zone: 1242624 pages, LIFO batch:31
Feb 07 11:54:25 ragnarok kernel: ACPI: PM-Timer IO Port: 0x408
Feb 07 11:54:25 ragnarok kernel: ACPI: Local APIC address 0xfee00000
Feb 07 11:54:25 ragnarok kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Feb 07 11:54:25 ragnarok kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Feb 07 11:54:25 ragnarok kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
Feb 07 11:54:25 ragnarok kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
Feb 07 11:54:25 ragnarok kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 07 11:54:25 ragnarok kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Feb 07 11:54:25 ragnarok kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Feb 07 11:54:25 ragnarok kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 07 11:54:25 ragnarok kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 07 11:54:25 ragnarok kernel: ACPI: IRQ0 used by override.
Feb 07 11:54:25 ragnarok kernel: ACPI: IRQ2 used by override.
Feb 07 11:54:25 ragnarok kernel: ACPI: IRQ9 used by override.
Feb 07 11:54:25 ragnarok kernel: Using ACPI (MADT) for SMP configuration information
Feb 07 11:54:25 ragnarok kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 07 11:54:25 ragnarok kernel: smpboot: Allowing 4 CPUs, 0 hotplug CPUs
Feb 07 11:54:25 ragnarok kernel: nr_irqs_gsi: 40
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0x40004000-0x40004fff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xc98c2000-0xc9f4cfff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xc9f4d000-0xca1ccfff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xca1cd000-0xca1d1fff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xca1d2000-0xca214fff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xcac0b000-0xcaff1fff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcb7fffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xcb800000-0xcf9fffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xcfa00000-0xf7ffffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Feb 07 11:54:25 ragnarok kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 07 11:54:25 ragnarok kernel: e820: [mem 0xcfa00000-0xf7ffffff] available for PCI devices
Feb 07 11:54:25 ragnarok kernel: Booting paravirtualized kernel on bare hardware
Feb 07 11:54:25 ragnarok kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
Feb 07 11:54:25 ragnarok kernel: PERCPU: Embedded 28 pages/cpu @ffff88022f200000 s83840 r8192 d22656 u524288
Feb 07 11:54:25 ragnarok kernel: pcpu-alloc: s83840 r8192 d22656 u524288 alloc=1*2097152
Feb 07 11:54:25 ragnarok kernel: pcpu-alloc: [0] 0 1 2 3
Feb 07 11:54:25 ragnarok kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2037744
Feb 07 11:54:25 ragnarok kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux-ck root=UUID=b5bc95f0-b132-4697-b135-7f972efcbf65 rw elevator=bfq resume=/dev/sdb1 init=/usr/lib/systemd/systemd
Feb 07 11:54:25 ragnarok kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 07 11:54:25 ragnarok kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 07 11:54:25 ragnarok kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Feb 07 11:54:25 ragnarok kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340
Feb 07 11:54:25 ragnarok kernel: Checking aperture...
Feb 07 11:54:25 ragnarok kernel: No AGP bridge found
Feb 07 11:54:25 ragnarok kernel: Calgary: detecting Calgary via BIOS EBDA area
Feb 07 11:54:25 ragnarok kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Feb 07 11:54:25 ragnarok kernel: Memory: 8055804K/8280452K available (4983K kernel code, 735K rwdata, 1608K rodata, 1108K init, 1264K bss, 224648K reserved)
Feb 07 11:54:25 ragnarok kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Feb 07 11:54:25 ragnarok kernel: Preemptible hierarchical RCU implementation.
Feb 07 11:54:25 ragnarok kernel: RCU dyntick-idle grace-period acceleration is enabled.
Feb 07 11:54:25 ragnarok kernel: Dump stacks of tasks blocking RCU-preempt GP.
Feb 07 11:54:25 ragnarok kernel: NR_IRQS:8448 nr_irqs:1704 16
Feb 07 11:54:25 ragnarok kernel: Console: colour dummy device 80x25
Feb 07 11:54:25 ragnarok kernel: console [tty0] enabled
Feb 07 11:54:25 ragnarok kernel: allocated 33554432 bytes of page_cgroup
Feb 07 11:54:25 ragnarok kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
Feb 07 11:54:25 ragnarok kernel: hpet clockevent registered
Feb 07 11:54:25 ragnarok kernel: tsc: Fast TSC calibration failed
Feb 07 11:54:25 ragnarok kernel: tsc: PIT calibration matches HPET. 1 loops
Feb 07 11:54:25 ragnarok kernel: tsc: Detected 3399.661 MHz processor
Feb 07 11:54:25 ragnarok kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6799.32 BogoMIPS (lpj=3399661)
Feb 07 11:54:25 ragnarok kernel: pid_max: default: 32768 minimum: 301
Feb 07 11:54:25 ragnarok kernel: Security Framework initialized
Feb 07 11:54:25 ragnarok kernel: AppArmor: AppArmor disabled by boot time parameter
Feb 07 11:54:25 ragnarok kernel: Yama: becoming mindful.
Feb 07 11:54:25 ragnarok kernel: Mount-cache hash table entries: 256
Feb 07 11:54:25 ragnarok kernel: Initializing cgroup subsys memory
Feb 07 11:54:25 ragnarok kernel: Initializing cgroup subsys devices
Feb 07 11:54:25 ragnarok kernel: Initializing cgroup subsys freezer
Feb 07 11:54:25 ragnarok kernel: Initializing cgroup subsys net_cls
Feb 07 11:54:25 ragnarok kernel: Initializing cgroup subsys blkio
Feb 07 11:54:25 ragnarok kernel: Initializing cgroup subsys bfqio
Feb 07 11:54:25 ragnarok kernel: CPU: Physical Processor ID: 0
Feb 07 11:54:25 ragnarok kernel: CPU: Processor Core ID: 0
Feb 07 11:54:25 ragnarok kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 07 11:54:25 ragnarok kernel: mce: CPU supports 9 MCE banks
Feb 07 11:54:25 ragnarok kernel: CPU0: Thermal monitoring enabled (TM1)
Feb 07 11:54:25 ragnarok kernel: Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
tlb_flushall_shift: 1
Feb 07 11:54:25 ragnarok kernel: Freeing SMP alternatives memory: 20K (ffffffff819ce000 - ffffffff819d3000)
Feb 07 11:54:25 ragnarok kernel: ACPI: Core revision 20130725
Feb 07 11:54:25 ragnarok kernel: ACPI: All ACPI Tables successfully acquired
Feb 07 11:54:25 ragnarok kernel: ftrace: allocating 20012 entries in 79 pages
Feb 07 11:54:25 ragnarok kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 07 11:54:25 ragnarok kernel: smpboot: CPU0: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (fam: 06, model: 3a, stepping: 09)
Feb 07 11:54:25 ragnarok kernel: TSC deadline timer enabled
Feb 07 11:54:25 ragnarok kernel: Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
Feb 07 11:54:25 ragnarok kernel: ... version: 3
Feb 07 11:54:25 ragnarok kernel: ... bit width: 48
Feb 07 11:54:25 ragnarok kernel: ... generic registers: 8
Feb 07 11:54:25 ragnarok kernel: ... value mask: 0000ffffffffffff
Feb 07 11:54:25 ragnarok kernel: ... max period: 0000ffffffffffff
Feb 07 11:54:25 ragnarok kernel: ... fixed-purpose events: 3
Feb 07 11:54:25 ragnarok kernel: ... event mask: 00000007000000ff
Feb 07 11:54:25 ragnarok kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 07 11:54:25 ragnarok kernel: smpboot: Booting Node 0, Processors # 1 # 2 # 3 OK
Feb 07 11:54:25 ragnarok kernel: Brought up 4 CPUs
Feb 07 11:54:25 ragnarok kernel: smpboot: Total of 4 processors activated (27197.28 BogoMIPS)
Feb 07 11:54:25 ragnarok kernel: devtmpfs: initialized
Feb 07 11:54:25 ragnarok kernel: PM: Registering ACPI NVS region [mem 0xc9f4d000-0xca1ccfff] (2621440 bytes)
Feb 07 11:54:25 ragnarok kernel: PM: Registering ACPI NVS region [mem 0xca1d2000-0xca214fff] (274432 bytes)
Feb 07 11:54:25 ragnarok kernel: RTC time: 11:54:24, date: 02/07/14
Feb 07 11:54:25 ragnarok kernel: NET: Registered protocol family 16
Feb 07 11:54:25 ragnarok kernel: cpuidle: using governor ladder
Feb 07 11:54:25 ragnarok kernel: cpuidle: using governor menu
Feb 07 11:54:25 ragnarok kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Feb 07 11:54:25 ragnarok kernel: ACPI: bus type PCI registered
Feb 07 11:54:25 ragnarok kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 07 11:54:25 ragnarok kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Feb 07 11:54:25 ragnarok kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Feb 07 11:54:25 ragnarok kernel: PCI: Using configuration type 1 for base access
Feb 07 11:54:25 ragnarok kernel: bio: create slab <bio-0> at 0
Feb 07 11:54:25 ragnarok kernel: ACPI: Added _OSI(Module Device)
Feb 07 11:54:25 ragnarok kernel: ACPI: Added _OSI(Processor Device)
Feb 07 11:54:25 ragnarok kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 07 11:54:25 ragnarok kernel: ACPI: Added _OSI(Processor Aggregator Device)
Feb 07 11:54:25 ragnarok kernel: ACPI: EC: Look up EC in DSDT
Feb 07 11:54:25 ragnarok kernel: ACPI: Executed 1 blocks of module-level executable AML code
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT 00000000c9efa018 0083B (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
Feb 07 11:54:25 ragnarok kernel: ACPI: Dynamic OEM Table Load:
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT (null) 0083B (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT 00000000c9efba98 00303 (v01 PmRef ApIst 00003000 INTL 20051117)
Feb 07 11:54:25 ragnarok kernel: ACPI: Dynamic OEM Table Load:
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT (null) 00303 (v01 PmRef ApIst 00003000 INTL 20051117)
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT 00000000c9efcc18 00119 (v01 PmRef ApCst 00003000 INTL 20051117)
Feb 07 11:54:25 ragnarok kernel: ACPI: Dynamic OEM Table Load:
Feb 07 11:54:25 ragnarok kernel: ACPI: SSDT (null) 00119 (v01 PmRef ApCst 00003000 INTL 20051117)
Feb 07 11:54:25 ragnarok kernel: ACPI: Interpreter enabled
Feb 07 11:54:25 ragnarok kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130725/hwxface-571)
Feb 07 11:54:25 ragnarok kernel: ACPI: (supports S0 S1 S3 S4 S5)
Feb 07 11:54:25 ragnarok kernel: ACPI: Using IOAPIC for interrupt routing
Feb 07 11:54:25 ragnarok kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 07 11:54:25 ragnarok kernel: ACPI: No dock devices found.
Feb 07 11:54:25 ragnarok kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Feb 07 11:54:25 ragnarok kernel: acpi PNP0A08:00: Requesting ACPI _OSC control (0x1d)
Feb 07 11:54:25 ragnarok kernel: acpi PNP0A08:00: ACPI _OSC control (0x1c) granted
Feb 07 11:54:25 ragnarok kernel: PCI host bridge to bus 0000:00
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:00.0: [8086:0150] type 00 class 0x060000
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:02.0: [8086:0162] type 00 class 0x038000
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:14.0: reg 0x10: [mem 0xf7b00000-0xf7b0ffff 64bit]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7b1a000-0xf7b1a00f 64bit]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7b18000-0xf7b183ff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7b10000-0xf7b13fff 64bit]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.3: [8086:1e16] type 01 class 0x060400
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.3: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.4: [8086:1e18] type 01 class 0x060400
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.5: [8086:1e1a] type 01 class 0x060400
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.7: [8086:1e1e] type 01 class 0x060400
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.7: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7b17000-0xf7b173ff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.0: [8086:1e44] type 00 class 0x060100
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.2: [8086:1e02] type 00 class 0x010601
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf0b0-0xf0b7]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf0a0-0xf0a3]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf090-0xf097]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf080-0xf083]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf060-0xf07f]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7b16000-0xf7b167ff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.2: PME# supported from D3hot
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7b15000-0xf7b150ff 64bit]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf040-0xf05f]
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.0: [10de:1189] type 00 class 0x030000
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.0: reg 0x14: [mem 0xe0000000-0xe7ffffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xe8000000-0xe9ffffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.1: [10de:0e0a] type 00 class 0x040300
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.1: reg 0x10: [mem 0xf7080000-0xf7083fff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
Feb 07 11:54:25 ragnarok kernel: pci 0000:03:00.0: [1b21:0612] type 00 class 0x010601
Feb 07 11:54:25 ragnarok kernel: pci 0000:03:00.0: reg 0x10: [io 0xd050-0xd057]
Feb 07 11:54:25 ragnarok kernel: pci 0000:03:00.0: reg 0x14: [io 0xd040-0xd043]
Feb 07 11:54:25 ragnarok kernel: pci 0000:03:00.0: reg 0x18: [io 0xd030-0xd037]
Feb 07 11:54:25 ragnarok kernel: pci 0000:03:00.0: reg 0x1c: [io 0xd020-0xd023]
Feb 07 11:54:25 ragnarok kernel: pci 0000:03:00.0: reg 0x20: [io 0xd000-0xd01f]
Feb 07 11:54:25 ragnarok kernel: pci 0000:03:00.0: reg 0x24: [mem 0xf7a00000-0xf7a001ff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.3: PCI bridge to [bus 03]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.3: bridge window [mem 0xf7a00000-0xf7afffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:04:00.0: [14e4:16b1] type 00 class 0x020000
Feb 07 11:54:25 ragnarok kernel: pci 0000:04:00.0: reg 0x10: [mem 0xea110000-0xea11ffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:04:00.0: reg 0x18: [mem 0xea100000-0xea10ffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:04:00.0: reg 0x30: [mem 0xf7900000-0xf79007ff pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.4: bridge window [mem 0xf7900000-0xf79fffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.4: bridge window [mem 0xea100000-0xea1fffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
Feb 07 11:54:25 ragnarok kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.5: PCI bridge to [bus 05-06]
Feb 07 11:54:25 ragnarok kernel: pci 0000:05:00.0: PCI bridge to [bus 06] (subtractive decode)
Feb 07 11:54:25 ragnarok kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
Feb 07 11:54:25 ragnarok kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
Feb 07 11:54:25 ragnarok kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
Feb 07 11:54:25 ragnarok kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
Feb 07 11:54:25 ragnarok kernel: pci 0000:07:00.0: [1b21:1042] type 00 class 0x0c0330
Feb 07 11:54:25 ragnarok kernel: pci 0000:07:00.0: reg 0x10: [mem 0xf7800000-0xf7807fff 64bit]
Feb 07 11:54:25 ragnarok kernel: pci 0000:07:00.0: PME# supported from D3hot D3cold
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.7: PCI bridge to [bus 07]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.7: bridge window [mem 0xf7800000-0xf78fffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: on NUMA node 0
Feb 07 11:54:25 ragnarok kernel: acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
Feb 07 11:54:25 ragnarok kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 07 11:54:25 ragnarok kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 07 11:54:25 ragnarok kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *10 11 12 14 15)
Feb 07 11:54:25 ragnarok kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 07 11:54:25 ragnarok kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 07 11:54:25 ragnarok kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Feb 07 11:54:25 ragnarok kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 07 11:54:25 ragnarok kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15)
Feb 07 11:54:25 ragnarok kernel: ACPI: Enabled 4 GPEs in block 00 to 3F
Feb 07 11:54:25 ragnarok kernel: ACPI: \_SB_.PCI0: notify handler is installed
Feb 07 11:54:25 ragnarok kernel: Found 1 acpi root devices
Feb 07 11:54:25 ragnarok kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
Feb 07 11:54:25 ragnarok kernel: vgaarb: loaded
Feb 07 11:54:25 ragnarok kernel: vgaarb: bridge control possible 0000:01:00.0
Feb 07 11:54:25 ragnarok kernel: PCI: Using ACPI for IRQ routing
Feb 07 11:54:25 ragnarok kernel: PCI: pci_cache_line_size set to 64 bytes
Feb 07 11:54:25 ragnarok kernel: e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
Feb 07 11:54:25 ragnarok kernel: e820: reserve RAM buffer [mem 0x40004000-0x43ffffff]
Feb 07 11:54:25 ragnarok kernel: e820: reserve RAM buffer [mem 0xc98c2000-0xcbffffff]
Feb 07 11:54:25 ragnarok kernel: e820: reserve RAM buffer [mem 0xcac0b000-0xcbffffff]
Feb 07 11:54:25 ragnarok kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
Feb 07 11:54:25 ragnarok kernel: e820: reserve RAM buffer [mem 0x22f600000-0x22fffffff]
Feb 07 11:54:25 ragnarok kernel: NetLabel: Initializing
Feb 07 11:54:25 ragnarok kernel: NetLabel: domain hash size = 128
Feb 07 11:54:25 ragnarok kernel: NetLabel: protocols = UNLABELED CIPSOv4
Feb 07 11:54:25 ragnarok kernel: NetLabel: unlabeled traffic allowed by default
Feb 07 11:54:25 ragnarok kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 07 11:54:25 ragnarok kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 07 11:54:25 ragnarok kernel: Switched to clocksource hpet
Feb 07 11:54:25 ragnarok kernel: pnp: PnP ACPI init
Feb 07 11:54:25 ragnarok kernel: ACPI: bus type PNP registered
Feb 07 11:54:25 ragnarok kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 07 11:54:25 ragnarok kernel: pnp 00:01: [dma 4]
Feb 07 11:54:25 ragnarok kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Feb 07 11:54:25 ragnarok kernel: pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
Feb 07 11:54:25 ragnarok kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
Feb 07 11:54:25 ragnarok kernel: system 00:04: [io 0x0680-0x069f] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:04: [io 0x0200-0x020f] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:04: [io 0xffff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:04: [io 0xffff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:04: [io 0x0400-0x0453] could not be reserved
Feb 07 11:54:25 ragnarok kernel: system 00:04: [io 0x0458-0x047f] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:04: [io 0x0500-0x057f] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:04: [io 0x164e-0x164f] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 07 11:54:25 ragnarok kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 07 11:54:25 ragnarok kernel: system 00:06: [io 0x0454-0x0457] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 07 11:54:25 ragnarok kernel: system 00:07: [io 0x0290-0x029f] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 07 11:54:25 ragnarok kernel: system 00:08: [io 0x04d0-0x04d1] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 07 11:54:25 ragnarok kernel: pnp 00:09: Plug and Play ACPI device, IDs PNP0c04 (active)
Feb 07 11:54:25 ragnarok kernel: pnp 00:0a: [dma 0 disabled]
Feb 07 11:54:25 ragnarok kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0501 (active)
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xfed10000-0xfed17fff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xfed18000-0xfed18fff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xfed19000-0xfed19fff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xf8000000-0xfbffffff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xfed45000-0xfed8ffff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xff000000-0xffffffff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xfee00000-0xfeefffff] could not be reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: [mem 0xcfa00000-0xcfa00fff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 07 11:54:25 ragnarok kernel: system 00:0c: [mem 0x20000000-0x201fffff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0c: [mem 0x40004000-0x40004fff] has been reserved
Feb 07 11:54:25 ragnarok kernel: system 00:0c: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 07 11:54:25 ragnarok kernel: pnp: PnP ACPI: found 13 devices
Feb 07 11:54:25 ragnarok kernel: ACPI: bus type PNP unregistered
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 02] add_size 200000
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xcfb00000-0xcfcfffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x2000-0x2fff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: bridge window [mem 0xcfb00000-0xcfcfffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.0: bridge window [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.3: PCI bridge to [bus 03]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.3: bridge window [mem 0xf7a00000-0xf7afffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.4: bridge window [mem 0xf7900000-0xf79fffff]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.4: bridge window [mem 0xea100000-0xea1fffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci 0000:05:00.0: PCI bridge to [bus 06]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.5: PCI bridge to [bus 05-06]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.7: PCI bridge to [bus 07]
Feb 07 11:54:25 ragnarok kernel: pci 0000:00:1c.7: bridge window [mem 0xf7800000-0xf78fffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 11 [mem 0x000e0000-0x000e3fff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 12 [mem 0x000e4000-0x000e7fff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 13 [mem 0x000e8000-0x000ebfff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:00: resource 14 [mem 0xcfa00000-0xfeafffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:01: resource 1 [mem 0xf6000000-0xf70fffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:01: resource 2 [mem 0xe0000000-0xe9ffffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:02: resource 0 [io 0x2000-0x2fff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:02: resource 1 [mem 0xcfb00000-0xcfcfffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:02: resource 2 [mem 0xcfd00000-0xcfefffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:03: resource 1 [mem 0xf7a00000-0xf7afffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:04: resource 1 [mem 0xf7900000-0xf79fffff]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:04: resource 2 [mem 0xea100000-0xea1fffff 64bit pref]
Feb 07 11:54:25 ragnarok kernel: pci_bus 0000:07: resource 1 [mem 0xf7800000-0xf78fffff]
Feb 07 11:54:25 ragnarok kernel: NET: Registered protocol family 2
Feb 07 11:54:25 ragnarok kernel: TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 07 11:54:25 ragnarok kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 07 11:54:25 ragnarok kernel: TCP: Hash tables configured (established 65536 bind 65536)
Feb 07 11:54:25 ragnarok kernel: TCP: reno registered
Feb 07 11:54:25 ragnarok kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
Feb 07 11:54:25 ragnarok kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Feb 07 11:54:25 ragnarok kernel: NET: Registered protocol family 1
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.0: Boot video device
Feb 07 11:54:25 ragnarok kernel: PCI: CLS 64 bytes, default 64
Feb 07 11:54:25 ragnarok kernel: Unpacking initramfs...
Feb 07 11:54:25 ragnarok kernel: Freeing initrd memory: 3056K (ffff8800379f8000 - ffff880037cf4000)
Feb 07 11:54:25 ragnarok kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 07 11:54:25 ragnarok kernel: software IO TLB [mem 0xc58c2000-0xc98c2000] (64MB) mapped at [ffff8800c58c2000-ffff8800c98c1fff]
Feb 07 11:54:25 ragnarok kernel: Scanning for low memory corruption every 60 seconds
Feb 07 11:54:25 ragnarok kernel: audit: initializing netlink socket (disabled)
Feb 07 11:54:25 ragnarok kernel: type=2000 audit(1391774064.186:1): initialized
Feb 07 11:54:25 ragnarok kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 07 11:54:25 ragnarok kernel: zbud: loaded
Feb 07 11:54:25 ragnarok kernel: VFS: Disk quotas dquot_6.5.2
Feb 07 11:54:25 ragnarok kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 07 11:54:25 ragnarok kernel: msgmni has been set to 15740
Feb 07 11:54:25 ragnarok kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 07 11:54:25 ragnarok kernel: io scheduler noop registered
Feb 07 11:54:25 ragnarok kernel: io scheduler deadline registered
Feb 07 11:54:25 ragnarok kernel: io scheduler cfq registered
Feb 07 11:54:25 ragnarok kernel: io scheduler bfq registered (default)
Feb 07 11:54:25 ragnarok kernel: BFQ I/O-scheduler version: v7
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.3: irq 42 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.4: irq 43 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.5: irq 44 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.7: irq 45 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.3: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pcie_pme 0000:00:1c.3:pcie01: service driver pcie_pme loaded
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pci 0000:04:00.0: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.5: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pcie_pme 0000:00:1c.5:pcie01: service driver pcie_pme loaded
Feb 07 11:54:25 ragnarok kernel: pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Feb 07 11:54:25 ragnarok kernel: pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Feb 07 11:54:25 ragnarok kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Feb 07 11:54:25 ragnarok kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Feb 07 11:54:25 ragnarok kernel: vesafb: mode is 2560x1440x32, linelength=10240, pages=0
Feb 07 11:54:25 ragnarok kernel: vesafb: scrolling: redraw
Feb 07 11:54:25 ragnarok kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Feb 07 11:54:25 ragnarok kernel: vesafb: framebuffer at 0xe9000000, mapped to 0xffffc90004100000, using 14400k, total 14400k
Feb 07 11:54:25 ragnarok kernel: Console: switching to colour frame buffer device 320x90
Feb 07 11:54:25 ragnarok kernel: fb0: VESA VGA frame buffer device
Feb 07 11:54:25 ragnarok kernel: intel_idle: MWAIT substates: 0x1120
Feb 07 11:54:25 ragnarok kernel: intel_idle: v0.4 model 0x3A
Feb 07 11:54:25 ragnarok kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Feb 07 11:54:25 ragnarok kernel: GHES: HEST is not enabled!
Feb 07 11:54:25 ragnarok kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Feb 07 11:54:25 ragnarok kernel: 00:0a: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Feb 07 11:54:25 ragnarok kernel: Linux agpgart interface v0.103
Feb 07 11:54:25 ragnarok kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Feb 07 11:54:25 ragnarok kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 07 11:54:25 ragnarok kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 07 11:54:25 ragnarok kernel: mousedev: PS/2 mouse device common for all mice
Feb 07 11:54:25 ragnarok kernel: rtc_cmos 00:05: RTC can wake from S4
Feb 07 11:54:25 ragnarok kernel: rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
Feb 07 11:54:25 ragnarok kernel: rtc_cmos 00:05: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Feb 07 11:54:25 ragnarok kernel: Intel P-state driver initializing.
Feb 07 11:54:25 ragnarok kernel: Intel pstate controlling: cpu 0
Feb 07 11:54:25 ragnarok kernel: Intel pstate controlling: cpu 1
Feb 07 11:54:25 ragnarok kernel: Intel pstate controlling: cpu 2
Feb 07 11:54:25 ragnarok kernel: Intel pstate controlling: cpu 3
Feb 07 11:54:25 ragnarok kernel: drop_monitor: Initializing network drop monitor service
Feb 07 11:54:25 ragnarok kernel: TCP: cubic registered
Feb 07 11:54:25 ragnarok kernel: NET: Registered protocol family 10
Feb 07 11:54:25 ragnarok kernel: NET: Registered protocol family 17
Feb 07 11:54:25 ragnarok kernel: Key type dns_resolver registered
Feb 07 11:54:25 ragnarok kernel: registered taskstats version 1
Feb 07 11:54:25 ragnarok kernel: Magic number: 2:556:933
Feb 07 11:54:25 ragnarok kernel: pcie_pme 0000:00:1c.3:pcie01: hash matches
Feb 07 11:54:25 ragnarok kernel: rtc_cmos 00:05: setting system clock to 2014-02-07 11:54:24 UTC (1391774064)
Feb 07 11:54:25 ragnarok kernel: PM: Checking hibernation image partition /dev/sdb1
Feb 07 11:54:25 ragnarok kernel: PM: Hibernation image not present or could not be loaded.
Feb 07 11:54:25 ragnarok kernel: Freeing unused kernel memory: 1108K (ffffffff818b9000 - ffffffff819ce000)
Feb 07 11:54:25 ragnarok kernel: Write protecting the kernel read-only data: 8192k
Feb 07 11:54:25 ragnarok kernel: Freeing unused kernel memory: 1148K (ffff8800014e1000 - ffff880001600000)
Feb 07 11:54:25 ragnarok kernel: Freeing unused kernel memory: 440K (ffff880001792000 - ffff880001800000)
Feb 07 11:54:25 ragnarok kernel: BFS CPU scheduler v0.444 by Con Kolivas.
Feb 07 11:54:25 ragnarok systemd-udevd[61]: starting version 208
Feb 07 11:54:25 ragnarok kernel: SCSI subsystem initialized
Feb 07 11:54:25 ragnarok kernel: libata version 3.00 loaded.
Feb 07 11:54:25 ragnarok kernel: ahci 0000:00:1f.2: version 3.0
Feb 07 11:54:25 ragnarok kernel: ahci 0000:00:1f.2: irq 46 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
Feb 07 11:54:25 ragnarok kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
Feb 07 11:54:25 ragnarok kernel: ahci 0000:00:1f.2: setting latency timer to 64
Feb 07 11:54:25 ragnarok kernel: scsi0 : ahci
Feb 07 11:54:25 ragnarok kernel: scsi1 : ahci
Feb 07 11:54:25 ragnarok kernel: scsi2 : ahci
Feb 07 11:54:25 ragnarok kernel: scsi3 : ahci
Feb 07 11:54:25 ragnarok kernel: scsi4 : ahci
Feb 07 11:54:25 ragnarok kernel: scsi5 : ahci
Feb 07 11:54:25 ragnarok kernel: ata1: SATA max UDMA/133 abar m2048@0xf7b16000 port 0xf7b16100 irq 46
Feb 07 11:54:25 ragnarok kernel: ata2: SATA max UDMA/133 abar m2048@0xf7b16000 port 0xf7b16180 irq 46
Feb 07 11:54:25 ragnarok kernel: ata3: SATA max UDMA/133 abar m2048@0xf7b16000 port 0xf7b16200 irq 46
Feb 07 11:54:25 ragnarok kernel: ata4: SATA max UDMA/133 abar m2048@0xf7b16000 port 0xf7b16280 irq 46
Feb 07 11:54:25 ragnarok kernel: ata5: SATA max UDMA/133 abar m2048@0xf7b16000 port 0xf7b16300 irq 46
Feb 07 11:54:25 ragnarok kernel: ata6: SATA max UDMA/133 abar m2048@0xf7b16000 port 0xf7b16380 irq 46
Feb 07 11:54:25 ragnarok kernel: ahci 0000:03:00.0: irq 47 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: ahci 0000:03:00.0: SSS flag set, parallel bus scan disabled
Feb 07 11:54:25 ragnarok kernel: ahci 0000:03:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
Feb 07 11:54:25 ragnarok kernel: ahci 0000:03:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs
Feb 07 11:54:25 ragnarok kernel: scsi6 : ahci
Feb 07 11:54:25 ragnarok kernel: scsi7 : ahci
Feb 07 11:54:25 ragnarok kernel: ata7: SATA max UDMA/133 abar m512@0xf7a00000 port 0xf7a00100 irq 47
Feb 07 11:54:25 ragnarok kernel: ata8: SATA max UDMA/133 abar m512@0xf7a00000 port 0xf7a00180 irq 47
Feb 07 11:54:25 ragnarok kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 07 11:54:25 ragnarok kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 07 11:54:25 ragnarok kernel: ata5: SATA link down (SStatus 0 SControl 300)
Feb 07 11:54:25 ragnarok kernel: ata3: SATA link down (SStatus 0 SControl 300)
Feb 07 11:54:25 ragnarok kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 07 11:54:25 ragnarok kernel: ata6: SATA link down (SStatus 0 SControl 300)
Feb 07 11:54:25 ragnarok kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 07 11:54:25 ragnarok kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 07 11:54:25 ragnarok kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 07 11:54:25 ragnarok kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 07 11:54:25 ragnarok kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 07 11:54:25 ragnarok kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 07 11:54:25 ragnarok kernel: ata7: SATA link down (SStatus 0 SControl 300)
Feb 07 11:54:25 ragnarok kernel: ata1.00: ATA-9: M4-CT128M4SSD2, 000F, max UDMA/100
Feb 07 11:54:25 ragnarok kernel: ata1.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 07 11:54:25 ragnarok kernel: ata2.00: ATA-9: WDC WD30EZRX-00DC0B0, 80.00A80, max UDMA/133
Feb 07 11:54:25 ragnarok kernel: ata2.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 07 11:54:25 ragnarok kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 07 11:54:25 ragnarok kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 07 11:54:25 ragnarok kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 07 11:54:25 ragnarok kernel: ata1.00: configured for UDMA/100
Feb 07 11:54:25 ragnarok kernel: scsi 0:0:0:0: Direct-Access ATA M4-CT128M4SSD2 000F PQ: 0 ANSI: 5
Feb 07 11:54:25 ragnarok kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 07 11:54:25 ragnarok kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 07 11:54:25 ragnarok kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 07 11:54:25 ragnarok kernel: ata2.00: configured for UDMA/133
Feb 07 11:54:25 ragnarok kernel: sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
Feb 07 11:54:25 ragnarok kernel: scsi 1:0:0:0: Direct-Access ATA WDC WD30EZRX-00D 80.0 PQ: 0 ANSI: 5
Feb 07 11:54:25 ragnarok kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 07 11:54:25 ragnarok kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 07 11:54:25 ragnarok kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 07 11:54:25 ragnarok kernel: sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 07 11:54:25 ragnarok kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 07 11:54:25 ragnarok kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 07 11:54:25 ragnarok kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 07 11:54:25 ragnarok kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 07 11:54:25 ragnarok kernel: sda: sda1 sda2 sda3 sda4
Feb 07 11:54:25 ragnarok kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 07 11:54:25 ragnarok kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 07 11:54:25 ragnarok kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 07 11:54:25 ragnarok kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 07 11:54:25 ragnarok kernel: ata4.00: ATA-8: ST1000DM005 HD103SJ, 1AJ10001, max UDMA/133
Feb 07 11:54:25 ragnarok kernel: ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Feb 07 11:54:25 ragnarok kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Feb 07 11:54:25 ragnarok kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Feb 07 11:54:25 ragnarok kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Feb 07 11:54:25 ragnarok kernel: ata4.00: configured for UDMA/133
Feb 07 11:54:25 ragnarok kernel: scsi 3:0:0:0: Direct-Access ATA ST1000DM005 HD10 1AJ1 PQ: 0 ANSI: 5
Feb 07 11:54:25 ragnarok kernel: sd 3:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Feb 07 11:54:25 ragnarok kernel: sd 3:0:0:0: [sdc] Write Protect is off
Feb 07 11:54:25 ragnarok kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Feb 07 11:54:25 ragnarok kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 07 11:54:25 ragnarok kernel: sdb: sdb1 sdb2
Feb 07 11:54:25 ragnarok kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 07 11:54:25 ragnarok kernel: sdc: sdc1 sdc2
Feb 07 11:54:25 ragnarok kernel: sd 3:0:0:0: [sdc] Attached SCSI disk
Feb 07 11:54:25 ragnarok kernel: tsc: Refined TSC clocksource calibration: 3400.026 MHz
Feb 07 11:54:25 ragnarok kernel: ata8: SATA link down (SStatus 0 SControl 300)
Feb 07 11:54:25 ragnarok kernel: ACPI: bus type USB registered
Feb 07 11:54:25 ragnarok kernel: usbcore: registered new interface driver usbfs
Feb 07 11:54:25 ragnarok kernel: usbcore: registered new interface driver hub
Feb 07 11:54:25 ragnarok kernel: usbcore: registered new device driver usb
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:00:14.0: setting latency timer to 64
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:00:14.0: irq 48 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: hub 1-0:1.0: USB hub found
Feb 07 11:54:25 ragnarok kernel: hub 1-0:1.0: 4 ports detected
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Feb 07 11:54:25 ragnarok kernel: hub 2-0:1.0: USB hub found
Feb 07 11:54:25 ragnarok kernel: hub 2-0:1.0: 4 ports detected
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:07:00.0: xHCI Host Controller
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:07:00.0: new USB bus registered, assigned bus number 3
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:07:00.0: irq 49 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:07:00.0: irq 50 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:07:00.0: irq 51 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:07:00.0: irq 52 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:07:00.0: irq 53 for MSI/MSI-X
Feb 07 11:54:25 ragnarok kernel: hub 3-0:1.0: USB hub found
Feb 07 11:54:25 ragnarok kernel: hub 3-0:1.0: 2 ports detected
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:07:00.0: xHCI Host Controller
Feb 07 11:54:25 ragnarok kernel: xhci_hcd 0000:07:00.0: new USB bus registered, assigned bus number 4
Feb 07 11:54:25 ragnarok kernel: hub 4-0:1.0: USB hub found
Feb 07 11:54:25 ragnarok kernel: hub 4-0:1.0: 2 ports detected
Feb 07 11:54:25 ragnarok kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Feb 07 11:54:25 ragnarok kernel: ehci-pci: EHCI PCI platform driver
Feb 07 11:54:25 ragnarok kernel: ehci-pci 0000:00:1a.0: setting latency timer to 64
Feb 07 11:54:25 ragnarok kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Feb 07 11:54:25 ragnarok kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus numb -
[SOLVED]Modem-manager won't start with Network manager
Hi,
I have a problem with getting modem-manager work under gnome. After first Arch install to this laptop, Network manager didn't show my 3G-modem, so I installed modem-manager and usb_modeswitch. Modem is Huawei E367 and it works well with wvdial. Only problem is to get it working with Network manager.
From output of dmesg I see that there is an error, when Network manager is trying to start modem-manager:
[ 3224.705193] do_trap: 322 callbacks suppressed
[ 3224.705198] modem-manager[3112] trap int3 ip:7ff7baab4143 sp:7fff996e62b0 error:0
[ 3224.719275] modem-manager[3114] trap int3 ip:7f58f4c5e143 sp:7fffc82b2400 error:0
[ 3224.733880] modem-manager[3116] trap int3 ip:7f579dda4143 sp:7fff77910850 error:0
[ 3224.748789] modem-manager[3118] trap int3 ip:7ff752c6f143 sp:7fff8ae42e20 error:0
[ 3224.763501] modem-manager[3120] trap int3 ip:7fb4db83f143 sp:7fff3023cbf0 error:0
[ 3224.777865] modem-manager[3122] trap int3 ip:7fa17a33a143 sp:7fffc1628260 error:0
[ 3224.792165] modem-manager[3124] trap int3 ip:7f00a39fb143 sp:7fff075a0fb0 error:0
[ 3224.806603] modem-manager[3126] trap int3 ip:7f9a62e23143 sp:7fffc2ccfed0 error:0
[ 3224.820736] modem-manager[3128] trap int3 ip:7f3d2994d143 sp:7ffff2581340 error:0
[ 3224.834985] modem-manager[3130] trap int3 ip:7f5adda9a143 sp:7fff8a70a4a0 error:0
From /var/log/messages.log I found also something:
Apr 14 16:02:14 localhost NetworkManager[713]: <info> trying to start the modem manager...
Apr 14 16:02:14 localhost dbus[651]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Apr 14 16:02:14 localhost dbus[651]: [system] Successfully activated service 'org.freedesktop.ModemManager'
Apr 14 16:02:14 localhost NetworkManager[713]: <info> modem-manager is now available
Apr 14 16:02:14 localhost modem-manager: libhal_ctx_init() failed: (null)
Apr 14 16:02:14 localhost NetworkManager[713]: <info> the modem manager disappeared
If I try to run modem-manager manually with debug:
$ sudo modem-manager --debug
** ERROR **: libhal_ctx_init() failed: (null)
Make sure the hal daemon is running?
So it seems to be because of hal isn't running, if I try to start hal daemon it fails:
$ sudo /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]
I also tried to start hal at boot by putting it to DAEMONS in rc.conf. but didn't start either.
The laptop is Asus X61SL with x86_64 version of ArchLinux.
Kernel: 3.3.1-1-ARCH
Would be cool if anyone can solve this.
Last edited by Jompu (2012-04-14 20:42:20)Thanks for your quick reply Strike0!
I ran lsusb and usb_modeswitch as you instructed:
[louis@Louis-Laptop ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
Bus 002 Device 002: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0
Bus 003 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 001 Device 006: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard
[louis@Louis-Laptop ~]$ sudo usb_modeswitch -v 12d1 -p 1506 -M '55534243123456780000000000000011062000000100000000000000000000'
Password:
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 006 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x82 (in)
Not a storage device, skipping SCSI inquiry
USB description data (for identification)
Manufacturer: Huawei Technologies
Product: HUAWEI Mobile
Serial No.: not provided
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x82
Resetting message endpoint 0x01
-> Run lsusb to note any changes. Bye.
It didn't help. Network manager doesn't show anything related 3G.
I don't think it's usb_modeswitch since 3G stick works great with wvdial on same system. Could it be a bug on modem-manager?
I start only the Network manager on boot, but while Network manager tries to start modem-manager, it throws error continuously in dmesg. Error is the same as in first post. -
Recovery manager won't start for clean reinstall of Windows 7
I have an HP Pavilion Elite HPE-110f that is 4 years old. Everything was fine until a couple of weeks ago started getting RAID messages on startup and other little qwerky things. Then last week the dreaded BSOD showed up. I shut down the computer and tried to restart, but got error messages that the computer couldn't start. I then tried everything I could think of - startup repair, tried to boot in safe mode, recovery from partitioned drive, system restore - nothing worked. I have the recovery media from HP but was saving that as my final option. I tried to do a clean reinstall today from the discs, but now the recovery manager won't even come up. Can somebody PLEASE help me get my OS back?
No, it wasn't an error message. It was just notifications about different things being accessed on port1. I just assumed it was startup items loading, but I had never gotten notifications about them before. I just tried again to reinstall from recovery discs. Pressed esc and got the boot menu, selected the dvd drive and you can hear it running, then it slows down to nothing and I get no recovery manager opening. I turned off the computer again and pressed f9 when I turned it on. Diagnostic show processor and memory are fine, but I get an error code of "BIOHD-8" on the hard drive. Any suggestions?
-
[SOLVED] PulseAudio Volume Control won't start anymore
Hi!
As described in the title, PulseAudio Volume Control won't start from one day to another.
I have no clue where this could come from or what I could have done wrong to create this issue.
Here is how it looks like:
When I start it, it seems to be loading but after some time it just disappears and nothing happens.
I also have the same looking issue with KMix and Google Music Manager.
Do any of you have an idea where this could be coming from?
Thanks for your help :-)
Last edited by StefanMu (2014-01-10 01:15:24)Rasi wrote:StefanMu, you are not giving enough details. Have there been any updates, that are pulse or gtk related. What versions do you have installed of gtk, gtkmm, libpulse, pavucontrol. Are all of those repository packages, or is something built from AUR? Any custom repositories?
Hi, and thanks for your reply. Here are the details:
gtk:
[root@ACDCROCKS-ARCH_LINUX miniclip22]# pacman -Qi gtk
Name : gtk
Version : 1.2.10-13
Description : GTK+ is a multi-platform toolkit (v1)
gtkmm:
[root@ACDCROCKS-ARCH_LINUX miniclip22]# pacman -Qi gtkmm
Name : gtkmm
Version : 2.24.4-1
Description : C++ bindings for gtk2
Architecture : x86_64
URL : [url]http://www.gtkmm.org/[/url]
libpulse:
[root@ACDCROCKS-ARCH_LINUX miniclip22]# pacman -Qi libpulse
Name : libpulse
Version : 4.0-6
Description : A featureful, general-purpose sound server (client library)
Architecture : x86_64
pavucontrol:
[root@ACDCROCKS-ARCH_LINUX miniclip22]# pacman -Qi pavucontrol
Name : pavucontrol
Version : 2.0-2
Description : A GTK volume control for PulseAudio
Architecture : x86_64
They are all repository packages, NOT from the AUR. As previously mentioned, this is a fresh install, so I don't have any custom repositories. Any help is appreciated. Thanks in advance!
Last edited by miniclip22 (2013-12-28 18:42:12) -
Android Studio SDK Manager Won't Start
I download the newest version of Android Studio from Google. You know there's something wrong to install it from AUR in China.
But when I click the SDK Manager button in Android Studio, the Manager does not start.
And then I go to the "android-studio/sdk/tools/" folder to run "./android"
$ ./android
The program 'Android SDK Manager' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 1968 error_code 8 request_code 139 minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Some infomation:
$ uname -a
Linux arch 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux
Thanks for your help:)Thanks very much for your reply.
But It does not work, while shows as followed
$ ./android --sync
Error: Flag '--sync' is not a valid global flag. Did you mean to specify it after the verb/object name?
Usage:
android [global options] action [action options]
Global options:
-s --silent : Silent mode, shows errors only.
-v --verbose : Verbose mode, shows errors, warnings and all messages.
--clear-cache: Clear the SDK Manager repository manifest cache.
-h --help : Help on a specific command.
Valid
actions
are
composed
of a verb
and an
optional
direct
object:
- sdk : Displays the SDK Manager window.
- avd : Displays the AVD Manager window.
- list : Lists existing targets or virtual devices.
- list avd : Lists existing Android Virtual Devices.
- list target : Lists existing targets.
- list device : Lists existing devices.
- list sdk : Lists remote SDK repository.
- create avd : Creates a new Android Virtual Device.
- move avd : Moves or renames an Android Virtual Device.
- delete avd : Deletes an Android Virtual Device.
- update avd : Updates an Android Virtual Device to match the folders
of a new SDK.
- create project : Creates a new Android project.
- update project : Updates an Android project (must already have an
AndroidManifest.xml).
- create test-project : Creates a new Android project for a test package.
- update test-project : Updates the Android project for a test package (must
already have an AndroidManifest.xml).
- create lib-project : Creates a new Android library project.
- update lib-project : Updates an Android library project (must already have
an AndroidManifest.xml).
- create uitest-project: Creates a new UI test project.
- update adb : Updates adb to support the USB devices declared in the
SDK add-ons.
- update sdk : Updates the SDK by suggesting new platforms to install
if available.
Napaim wrote:
Did you recently do a system update?
From searching around it seems like it's a graphical problem or a font problem.
Also maybe try running `./android --sync` just to see if there's a different output. -
After doing a fresh install of Cisco Prime 4.1 and rebooting the server 'Cisco Prime Daemon Manager' service won't start. Startup type is 'Auto'. Server has been rebooted twice and I have tried 'net start crmdmgtd' without success.
C:\Users\NetAdmin>net start crmdmgtd
The Cisco Prime Daemon Manager service is starting.
The Cisco Prime Daemon Manager service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
C:\Users\NetAdmin>net helpmsg 3534
The service did not report an error.
C:\Users\NetAdmin>I need to see following output:
> Output when you enter command : net start crmdmgtd (on command prompt)
> Last 100 lines of NMSROOT/log/syslog.log
> event logs, if anything pertainign to Ciscoworks processes.
Try following things as well:
# Make casuser a member of adminitrators group.
#Make sure you have swap properly and manually configured (twice of RMA):
1. Right click on "Computer" and select "Properties." Click on "Advanced System Settings."
2. Choose the "Advanced" tab and click "Settings," under "Performance."
3. Choose the "Advanced" tab and click "Change" under "Virtual Memory."
4. Uncheck "Automatically Manage Paging File Size" for all drives.
5. Click "Custom Size" and enter the amount of swap space in MB (megabytes). Click "Set" and then "OK" three times to return to the desktop.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. ** -
Desktop manager won't start, sometimes
Edit: I have migrated from kdm to sddm and the problem is just the same.
I have a really weird problem with my laptop (Lenovo E335):
Sometimes, when I boot/reboot my laptop, kdm is started correctly, but other times (maybe more often) kdm won't start, and I need to login as root in a terminal, and run:
$ systemctl restart kdm
After doing this, kdm is always restarted correctly.
Whenever I boot/reboot the system, before kdm is started or fails, I see always these text lines in the console:
[FAILED] Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video
See "systemctl status systemd-backlight@backlight:acpi_video2.service" for details.
Starting Load/Save Screen Backlight Brightness of backlight:radeon_bl0...
[OK] Started Load/Save Screen Backlight Brightness of backlight:radeon_bl0.
When kdm fails, the boot process ends with this screen, and then I have to press Ctrl+Alt+F1 to open the terminal.
When this happens, these lines can be read in /var/log/Xorg.0.log:
(EE) Screen0 deleted because no matching config section.
(II) UnloadModule: "radeon".
(EE) Device(s) detected, but none match those in the config file.
(EE) no screens found(EE)
What puzzles me is that this only happens sometimes, apparently randomly.
--mod note: changed img tags to url tags. -- WorMzy
Last edited by fahrgast (2015-05-13 20:40:02)Hi fahrgast, welcome to Arch.
Please take a moment to read through the forum etiquette, paying particular attention to the section titled "Pasting pictures and code".
https://wiki.archlinux.org/index.php/Forum_etiquette
Thanks. -
[Solved] Fresh install; HAL won't start?
So I just finished a fresh installation and now I can't start X because HAL won't start up at all.
I haven't messed around with anything except for installing everything and fixing up my config files.
Seems like HAL is crashing because of permissions but I even checked the paths and they seem to be fine:
hald --daemon=no --verbose=yes
01:08:41.090 [i] hald.c:673: hal 0.5.14
01:08:41.090 [i] hald.c:674: using child timeout 250s
01:08:41.090 [i] hald.c:739: Will not daemonize
01:08:41.090 [i] hald_dbus.c:5444: local server is listening at unix:abstract=/var/run/hald/dbus-uBDySnOMjt,guid=33e68e9ab5cc00ac1ce4ba92000008c1
01:08:41.091 [i] hald_runner.c:304: Runner has pid 1695
Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
01:08:41.093 [i] hald_runner.c:184: runner connection is 0x17da830
01:08:41.097 [W] osspec.c:393: Unable to open /proc/mdstat: No such file or directory
** (process:1694): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/preprobe': Permission denied
** (process:1694): WARNING **: Failed to add monitor on '/etc/hal/fdi/preprobe': Permission denied
** (process:1694): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/information': Permission denied
** (process:1694): WARNING **: Failed to add monitor on '/etc/hal/fdi/information': Permission denied
** (process:1694): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/policy': Permission denied
** (process:1694): WARNING **: Failed to add monitor on '/etc/hal/fdi/policy': Permission denied
22:08:41.098 [i] mmap_cache.c:126: Regenerating fdi cache..
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry
22:08:41.099 [E] hald_runner.c:888: Error running 'hald-generate-fdi-cache': org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
22:08:41.099 [i] mmap_cache.c:104: In regen_cache_cb exit_type=2, return_code=0
22:08:41.099 [E] mmap_cache.c:153: fdi cache regeneration failed!
22:08:41.099 [i] mmap_cache.c:156: fdi cache generation done
22:08:41.099 [i] mmap_cache.c:278: cache mtime is 0
*** [DIE] osspec.c:osspec_init():449 : Unable to read /proc/mounts
Can't find anything worthwhile in logs etc., and I can't think of anything that could be causing this?
I checked that the HAL user exists and has been added to the default groups, but that "???"-part is alarming.
DBus starts up normally.
Networking and "lo" seem to be working fine as well, and I don't have iptables up.
Last edited by initbox (2011-07-05 16:59:36)tomk wrote:Update your system - xorg does not depend on hal anymore. hal is obsolete.
Ah, haven't been up to date on all the changes, it seems...
In the past I've had problems with the nvidia driver + Xorg without HAL, I think?
Anyhow, contrary to the Xorg page, I had no 20-nvidia.conf. I created that and now I'm able to startx without HAL but KDM doesn't work, the screen flickers when it attempts to start Xorg but then it crashes. Strange. Nothing in the Xorg logs either.
I'll have to see about that next, but it's nice to be able to get rid of HAL at least. -
[SOLVED] systemd display-manager.service problem
Hi!
After the upgrade of systemd, i noticed today this error in dmesg:
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.
systemctl status display-manager.service
display-manager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
Any idea?
Thanks!
EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
Last edited by nierro (2012-07-15 17:13:42)nierro wrote:
Hi!
After the upgrade of systemd, i noticed today this error in dmesg:
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.
systemctl status display-manager.service
display-manager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
Any idea?
Thanks!
EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
There has been a change regarding display managers. up until now they were WantedBy graphical.target, which was kind of stupid because this allowed you to enable multiple display managers.
Instead graphical.target now Wants display-manager.service and all display managers are supposed to install the appropriate Alias. Afaik all display manager service files have been updated ragarding this and a "systemctl reenable slim.service" should fix it. -
Windows 7 Won't Start Up from Boot Camp
I got a new 21.5" iMac and set up a boot camp partition for a Windows 7 64-bit installation. It worked. I installed the latest boot camp drivers into the Windows 7, which was wonderful because it fixed the display to match my iMac's specs. Then I installed the latest Parallels 5 and had it recognize that Windows 7 system, and have been using it without problem. But I tried this evening to use boot camp to start up the Windows 7 system by itself and although I got a choice of Mac OS or Windows via the option-startup process, and selected the Windows startup, Windows 7 won't start up that way. I just get a black screen with a blinking white horizontal line in the upper-left corner. I keep waiting but it never gets past this. Tried turning it off and starting again, still no luck. Booted back into Mac side and Parallels VM of the installation still works.
Any help appreciated. I should still be able to boot into Windows 7 straight using boot camp, no?I should add that I just installed 8GB of RAM to the 4GB the iMac came with. Possibly now that the total machine has a 12GB of RAM the Windows 7 system is confused and can't start up?
-
After 10.4.11 upgrade Macbook won't start can't boot from external HD
Hi guys,
I just suffer as all other that after try ti install the 10.4.11 update my macbook won't start, I have a external HD with a image of my macbook but went I press and hold the option key I only see the bootcamp parttion and my internal HD, I don't see the external HD.
How can I boot from my external HD if I have a bootcamp partition?
ThanksI follow the robotobi post and solve this issue.
Thanks robotobi
Maybe you are looking for
-
Creating PL/SQL package in SQL Developer 4.0.0.12
Hi, I have built a model in SQL Developer 4.0.0.12 and I want to create it's PL/SQL package. In ODMiner 11.1.0.4 from "Tools" > "Create pl/sql package" I can get a script for creating package and every thing is OK. but in SQL Developer I select "Depl
-
My Macbook wireless no longer works with my D-Link router
I purchased my Macbook in the summer of 2006 and have been using it wirelessly with a D-Link Airplus Xtreme G (DI-624) router. Just recently it stopped working with my router, although if I turn encryption off or try it in coffee shops, etc, the wire
-
How to make line-in come out rear speakers? (SB Live! 5
Card is SB Li've! 5. DE and OS is XP SP2: ================================ I have tried everything that I can think of. It was working fine until I installed a program which screwed up my mixer settings. I have loaded the default mixer settings. Now
-
Ipod reset and restore wont help
Hi, well hope somebody helps me out of this. i love my ipod and its throwing tantrums at me.. Anyway well suddenly d ipod dint start. it kept showing the charging symbol even when not connected.. so did a reset and still the same.. Then i tried it to
-
Portal Runtime error - Customization
Hi, How to customize the Portal runtime error message page in portal. Is it required to modify any standard par file for this? If so what par file needs to be modified. Ramganesan Karuppaiyah