Systemd kills my network on shutdown before nfs is unmounted
My home-directory is on nfs and I've been having this issue for a couple of months now; when shutting down systemd will stop my network without waiting for nfs unmounts to complete This results in incomplete shutdowns which sometimes take more then 10 minutes. It looks like this:
Nov 15 10:52:26 desktop systemd[1]: Stopped RPC GSS-API client-side daemon.
Nov 15 10:52:26 desktop systemd[1]: Unmounting RPC pipe filesystem...
Nov 15 10:52:26 desktop systemd[1]: Stopping RPC Bind...
Nov 15 10:52:26 desktop rpcbind[454]: rpcbind terminating on signal. Restart with "rpcbind -w"
Nov 15 10:52:26 desktop rpcbind[454]: cannot open file = /run/rpcbind.xdr for writing
Nov 15 10:52:26 desktop rpcbind[454]: cannot save any registration
Nov 15 10:52:26 desktop rpcbind[454]: cannot open file = /run/portmap.xdr for writing
Nov 15 10:52:26 desktop rpcbind[454]: cannot save any registration
Nov 15 10:52:26 desktop systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 15 10:52:26 desktop systemd[1]: Stopped RPC Bind.
Nov 15 10:52:26 desktop systemd[1]: Unit rpcbind.service entered failed state.
Nov 15 10:52:26 desktop systemd[1]: Stopped Login Service.
Nov 15 10:52:26 desktop umount[3604]: umount: /home/user: not mounted
Nov 15 10:52:26 desktop systemd[1]: home-user.mount mount process exited, code=exited status=32
Nov 15 10:52:26 desktop systemd[1]: Unmounted /home/user.
Nov 15 10:52:26 desktop systemd[1]: Unit home-user.mount entered failed state.
Nov 15 10:52:26 desktop systemd[1]: Unmounted RPC pipe filesystem.
Nov 15 10:52:26 desktop systemd[1]: mnt-bigdisk.mount mount process exited, code=exited status=32
Nov 15 10:52:26 desktop systemd[1]: Unmounted /mnt/bigdisk.
Nov 15 10:52:26 desktop systemd[1]: Unit mnt-bigdisk.mount entered failed state.
Nov 15 10:52:26 desktop systemd[1]: Stopping Network is Online.
Nov 15 10:52:26 desktop systemd[1]: Stopped target Network is Online.
Nov 15 10:52:26 desktop systemd[1]: Stopping Network.
Nov 15 10:52:26 desktop systemd[1]: Stopped target Network.
Nov 15 10:52:26 desktop systemd[1]: Stopping dhcpcd on enp3s0...
Nov 15 10:52:26 desktop umount[3605]: umount: /mnt/bigdisk: not mounted
Nov 15 10:52:26 desktop dhcpcd[3623]: dhcpcd[3623]: sending signal 15 to pid 414
Nov 15 10:52:26 desktop dhcpcd[3623]: dhcpcd[3623]: waiting for pid 414 to exit
Nov 15 10:52:26 desktop dhcpcd[3623]: sending signal 15 to pid 414
Nov 15 10:52:26 desktop dhcpcd[3623]: waiting for pid 414 to exit
Nov 15 10:52:26 desktop dhcpcd[414]: received SIGTERM from PID 3623, stopping
Nov 15 10:52:26 desktop dhcpcd[414]: enp3s0: removing interface
Nov 15 10:52:26 desktop dhcpcd[414]: enp3s0: deleting host route to 192.168.1.12 via 127.0.0.1
Nov 15 10:52:26 desktop dhcpcd[414]: enp3s0: deleting route to 192.168.1.0/24
Nov 15 10:52:26 desktop dhcpcd[414]: enp3s0: deleting default route via 192.168.1.254
Nov 15 10:52:26 desktop systemd[1]: Stopped User Manager for 1000.
Nov 15 10:52:26 desktop systemd[1]: Stopping user-1000.slice.
Nov 15 10:52:26 desktop systemd[1]: Removed slice user-1000.slice.
Nov 15 10:52:26 desktop dhcpcd[414]: exited
Nov 15 10:52:26 desktop systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
Nov 15 10:52:26 desktop systemd[1]: Stopped dhcpcd on enp3s0.
Nov 15 10:52:26 desktop systemd[1]: Unit [email protected] entered failed state.
Nov 15 10:52:26 desktop systemd[1]: Stopping system-dhcpcd.slice.
Nov 15 10:52:26 desktop systemd[1]: Removed slice system-dhcpcd.slice.
Nov 15 10:52:27 desktop systemd[1]: slim.service: main process exited, code=exited, status=1/FAILURE
Nov 15 10:52:27 desktop systemd[1]: Stopped SLiM Simple Login Manager.
Nov 15 10:52:27 desktop systemd[1]: Unit slim.service entered failed state.
Nov 15 10:52:27 desktop systemd[1]: Stopping Permit User Sessions...
Nov 15 10:52:27 desktop systemd[1]: Stopping Local File Systems.
Nov 15 10:52:27 desktop systemd[1]: Stopped target Local File Systems.
Nov 15 10:52:27 desktop systemd[1]: Unmounting /home...
Nov 15 10:52:27 desktop systemd[1]: Unmounting /var/backup...
Nov 15 10:52:27 desktop systemd[1]: Unmounting /tmp...
Nov 15 10:52:27 desktop umount[3666]: umount: /home: target is busy
Nov 15 10:52:27 desktop umount[3666]: (In some cases useful info about processes that
Nov 15 10:52:27 desktop umount[3666]: use the device is found by lsof(8) or fuser(1).)
Nov 15 10:52:27 desktop systemd[1]: home.mount mount process exited, code=exited status=32
Nov 15 10:52:27 desktop systemd[1]: Failed unmounting /home.
Nov 15 10:52:27 desktop systemd[1]: Unmounted /tmp.
Nov 15 10:52:27 desktop systemd[1]: Unmounted /var/backup.
Nov 15 10:52:27 desktop systemd[1]: Starting Unmount All Filesystems.
Nov 15 10:52:27 desktop systemd[1]: Reached target Unmount All Filesystems.
Nov 15 10:52:27 desktop systemd[1]: Stopping Local File Systems (Pre).
Nov 15 10:52:27 desktop systemd[1]: Stopped target Local File Systems (Pre).
Nov 15 10:52:27 desktop systemd[1]: Stopping Remount Root and Kernel File Systems...
Nov 15 10:52:27 desktop systemd[1]: Stopped Remount Root and Kernel File Systems.
Nov 15 10:52:27 desktop systemd[1]: Starting Shutdown.
Nov 15 10:52:27 desktop systemd[1]: Reached target Shutdown.
Nov 15 10:52:27 desktop systemd[1]: Starting Final Step.
Nov 15 10:52:27 desktop systemd[1]: Reached target Final Step.
Nov 15 10:52:27 desktop systemd[1]: Starting Reboot...
Nov 15 10:52:27 desktop systemd[1]: Shutting down.
Nov 15 10:52:27 desktop sudo[3600]: pam_unix(sudo:session): session closed for user root
Nov 15 10:52:27 desktop systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Nov 15 10:52:27 desktop systemd[1]: Set hardware watchdog to 10min.
Nov 15 10:52:27 desktop kernel: watchdog watchdog0: watchdog did not stop!
Nov 15 10:52:27 desktop systemd-journal[144]: Journal stopped
Does systemd have any notion of a relation between the network connection and the filesystem that is mounted via that connection? Because it seems to treat the filesystem equal to a local filesystem which it clearly isn't.
Relevant parts:
/dev/sda2 / ext4 defaults,discard 0 1
none /tmp tmpfs nodev,nosuid,noatime,size=4G,mode=1777
/dev/md1 /home ext4 defaults 0 3
server:/var/cache/pacman /var/cache/pacman nfs4 exec,auto
server:/srv /srv nfs4 defaults,auto
server:/home/user /home/user nfs4 exec,auto
Last edited by Spider.007 (2013-11-23 12:46:19)
Similar Messages
-
How to run something on shutdown before file systems unmounted
I've been trying to get kexec working with systemd, following the advice on this wiki page:
https://wiki.archlinux.org/index.php/Kexec#Systemd
Unfortunately, the suggested unit file does not work for me. The problem is that no matter what I do, my /boot file system gets unmounted before kexec gets run (so that it cannot find the kernel). I've tried adding most subsets of the following to the Unit section of my [email protected] file, all to no avail:
Before=shutdown.target umount.target final.target
RequiresMountsFor=/boot/vmlinuz-linux
Wants=boot.mount
After=boot.mount
If I run "systemctl start kexec-load@linux" followed by "systemctl kexec", everything works fine. But if I forget to do the former, then the kexec fails.
Anyway, I'm finding it super frustrating not to be able to control the order of events on shutdown. There has to be a way to do it, but absolutely nothing I've tried seems to make any difference. On startup I can obviously control things, so I could have some dummy service that does nothing on start but on stop calls kexec. But I don't want kexec called on an ordinary reboot or poweroff, only after "systemctl kexec."
If someone could tell me how to do what I need to do, I would much appreciate it.use:
FileOutputStream data_Stream = new FileOutputStream(data_File, true);The second argument is the append flag and is false by default. -
"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 furtherDuring 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 -
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 -
My desk top was infected and shutdown before I could do anything. How can I transfer all my music, movies, films, pictures and apps to another computer?
If there was no backup, where would you recover the photos from. Sorry but those pictures are gone.
-
Hi, I've seen a number of threads in the past about iTunes killing the network. I'm trying to download the latest firmware for my iPad (4.3.2) but I am unable to do so as my network dies. It only happens when I use iTunes. I am on an ADSL Router, and it seems that it kills my connection between my PC (10.1.1.3) and my router/gateway (10.1.1.1) As I type, my PC has been happily pinging the default gateway for 30 minutes now, but as soon as I try to download apps or the firmware, anytime between immediately and 60 seconds, it starts displaying "General Failure" and "Request timed out" randomly until it dies. I then get random replies of "Reply from 10.1.1.3: Destination host unreachable." The firmware won't allow me to resume the download after it dies, which make it that much more difficult.
I have also tried updating from version 7 to 8 Itunes. This did not fix the issue.
-
Is Killer Network actually Killing My Network?
Hello All,
I have been running into issues this past week after a recent computer build. One of my computers either is having Video Card Issues, or Network Issues.
I have a "Lan Center" that I have built over the years in my basement. Ever since the early Beta Counterstrike days I have always ran more than 1 computer in my household. Most of my friends are broke hippies, but I work in IT and enjoy playing once in a while.
The Game : GTA V for PC
The Problem : When going high speeds in vehicles, or when in big online lobby's. The framerate either drops (I don't know how to monitor FPS on this game as of yet) or my network is dying. On the other two PC's when in a private lobby, I can watch this PC lag in game. It will start off fine, but jump in a Bugatti, and it all goes to hell.
The Hardware :
Computer 1 -
CPU -i7-5820K (No OC)
Video - EVGA GTX 970 (No OC)
Mobo - ASRock X99X
HDD - Samsung 850 Pro 512gb
Ram - Crucial 16GB DDR4
PSU - Corsair AX760
CPU Cooler - Corsair H75
Sound - Creative SB ZxR
Case - NZXT H440
OS - Win 7 64bit Pro
Computer 2 -
MSI GT60 20D-026US Laptop
CPU - i7 4700MQ (No OC)
Video - GTX 780m (No OC)
HDD - Samsung 840 EVO 500gb
Ram - 16GB DDR3
OS - Win 8.1 64bit
Computer 3 -
CPU - i7-4790K (No OC)
Video - Radeon HD7870 (No OC)
Mobo - MSI Z97-GD65
HDD - WD Black 1TB
Ram - Kingston 8GB DDR3
PSU - EVGA 750G2
CPU Cooler - Stock
Case - NZXT H440
OS - Win 7 64bit Pro
Network Equipment -
Connection - Comcast 50/10
Modem - Motorola SB6121
Router - Netgear N750
Troubleshooting : I have already updated all of the drivers for the current hardware. I have already ran ALL windows updates. I have already ran Speccy on the culprit pc (Computer 3). All idle temps are fine, I left it running while running the game and all temps appear to be fine then as well. What I don't understand is the network graph, while in game it shows HUGE spikes and inconsistency. Thinking it could be a network cable, I replaced it with a new one. I just don't understand why this computer would spike and the other two don't. Another possibility is, when building this computer, it was basically a swap from my main computer. I never uninstalled the drivers for my GTX 970, so I guess there is a possibility that that is causing the video issue. All have Killer NIC cards. So stands my question. Is Killer Network, killing my network? Any help would be greatly appreciated. Also, any tips on buffing up my network would be great as well. Thanks in advance!I am with JLio01 on this. Try the Killer Network driver without the application and see if that fixes the issue.
There is not really any reason that it should lag like that. -
Officejet 150 Mobile Error "Printer shutdown before the original was removed...
Display Error: Printer shutdown before the original was removed. Remove the original to continue
I've tried everything to get the to go away! Help...anybody! Thank You!Hi @moosefood , and welcome to the HP Forums!
I can see from your post that you're experiencing printer errors. I'd like to help!
Before we get started, I need a little info. I am linking a few HP Support documents below that will show you how to find which operating system you are using. Also, if you're using Windows, please include whether your operating system is 32-bit or 64-bit.
Mac OS X: How Do I Find Which Mac OS X Version Is on My Computer?
Which Windows operating system am I running?
Is the Windows Version on My Computer 32-bit or 64-bit?
In the meantime, I'd recommend a power reset. Disconnect the power cord from the printer and the power outlet, then wait 60 seconds. After 60 seconds, plug the printer back in. Ensure you plug the printer directly to a wall outlet. Make sure to bypass any sort of surge protector or power bar.
Please let me know what you find. Thanks for posting on the HP Forums!
Please click “Accept as Solution " if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks" for helping!
Jamieson
I work on behalf of HP
"Remember, I'm pulling for you, we're all in this together!" - Red Green. -
Hyper V file transfer kills the network
Dear All,
We have 4 Hyper V VM installations on 2 HP DL 380 G8 servers and have they are connected to HP NSA 2040 SAN Storage through 6 Gbps Fibre channel. The physical machines are clustered.
Out of the 4, 2 are Clustered Hyper V's running Microsoft Dynamics AX 2012 R3 and we have 2 Clustered Hyper V for Database server running MS SQL 2012 R2.
The issue here is that the APP servers are slow in communicating with the DB server. The Hyper V's have a dedicated 4 * 1Gbps interface cards teamed and the packets are getting timed out. But from any other machine in the subnet the communications are proper.
When ever i try to copy a file from the DB server to the APP server using SMB share it kills my network, the copy will happen but after the copy is completed the network comes backup.
Its strange scenario. APP server 2 APP server smb copy is fine, and from DB to DB smb copy is fine but cannot copy between them.
Can anyone please help?
Thanks,
Sriram A DasHello,
This forum is for discussions and questions regarding profiles and Microsoft's recognition system on the MSDN and TechNet sites. It is not for products/technologies.
As it's off-topic here, I am moving the question to the
Hyper-V forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}}) -
Chat SSDP Discovery flooding network killing all networking
I am having a huge issue with the latest version of iChat. When I start it up it sends out 10,000 to 20,000 SSDP requests to 239.255.255.250. If I shut down iChat it continues for about a minute then stops and everything is back to normal. Tried changing the ports.
We are using NAT on a Windows 2003 server.
This kills the network and no other network traffic happens.
When I run iChat at home it all works fine, without a problem. It is only when I am in the office.
My office setup is DHCP from a Windows 2003 R2 x64 server and all network traffic is routed through this server via NAT.
It has been working fine in the office for about a year and all three macs worked fine. Now all three have the same issue.
A network sniff with WireShark shows that my mac sends a MDNS query to 224.0.0.251 then to 10.x.x.x which is the server. but the one to the server is designated a malformated packet.
My mac then sends a SSDP request to 10.x.x.x
The server replies with an ICMP packet saying the port it not reachable
My mac then sends out another request to the server
Then it sends out a SSDP request to 239.255.255.250 and continues doing so killing the network.
This is part of the packet trace
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover"Hi Ralph
Thanks but no joy.
Some more background information:
When I run iChat at home it all works fine, without a problem. It is only when I am in the office.
My office setup is DHCP from a Windows 2003 R2 x64 server and all network traffic is routed through this server via NAT.
It has been working fine in the office for about a year and all three macs worked fine. Now all three have the same issue.
A network sniff with WireShark shows that my mac sends a MDNS query to 224.0.0.251 then to 10.x.x.x which is the server. but the one to the server is designated a malformated packet.
My mac then sends a SSDP request to 10.x.x.x
The server replies with an ICMP packet saying the port it not reachable
My mac then sends out another request to the server
Then it sends out a SSDP request to 239.255.255.250 and continues doing so killing the network.
This is part of the packet trace
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover" -
IChat SSDP Discovery flooding network killing all networking.
I am having a huge issue with the latest version of iChat. When I start it up it sends out 10,000 to 20,000 SSDP requests to 239.255.255.250. If I shut down iChat it continues for about a minute then stops and everything is back to normal. Tried changing the ports.
We are using NAT on a Windows 2003 server.
This kills the network and no other network traffic happens.
This has only just started in the last week.Hi Ralph
Thanks but no joy.
Some more background information:
When I run iChat at home it all works fine, without a problem. It is only when I am in the office.
My office setup is DHCP from a Windows 2003 R2 x64 server and all network traffic is routed through this server via NAT.
It has been working fine in the office for about a year and all three macs worked fine. Now all three have the same issue.
A network sniff with WireShark shows that my mac sends a MDNS query to 224.0.0.251 then to 10.x.x.x which is the server. but the one to the server is designated a malformated packet.
My mac then sends a SSDP request to 10.x.x.x
The server replies with an ICMP packet saying the port it not reachable
My mac then sends out another request to the server
Then it sends out a SSDP request to 239.255.255.250 and continues doing so killing the network.
This is part of the packet trace
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover" -
Strange Shutdown Before Sleep & Airport Network Corruption
I'm having a very odd problem and I can't seem to find any resolve. Hopefully someone can provide some kind of insight.
I have a PowerBook G4 1.5GHz running OS X 10.5.6. I connect to OS X Server when at the office. I've owned the machine since August 2005 and it's no longer under warranty. I received a replacement battery from Apple for my original battery when it was recalled. The replacement battery was conditioned upon receiving it but it has never had the same kind of life as the original battery that came with the PowerBook, although it definitely runs cooler.
I didn't notice any issues running under Tiger and have only noticed that problems began under one of the Leopard updates, although not exactly sure which one it started under.
The issue seems to be largely with the system not going to sleep when on low battery, but instead, simply shutting itself down. I get the low battery warning, but if I just let it go, the system will eventually shut down without warning. It has occasionally shut down with about 20% battery life left on the power reading in the menu bar.
When I connect a power source and start the computer back up, the date has been reset, indicating that the machine has died completely.
Here's the really strange part. The last wireless network I was connected to seems to now be corrupt and I have to remove it from my Airport preferred networks and add it fresh. It's as if the password is not the same and it prompts me for the password again, it doesn't keep it saved and I have to enter it every time I connect to that network.
For the shut down before sleeping part and the clock resetting, is it just that the battery on the logic board needs to be replaced because it's dead?
On the shutting down before sleeping issue, is anyone else having this same problem?
As for the Airport corruption, does anyone have any ideas?I am having the same problem - I have 20% battery and then the computer shuts downs and when I restart the date & time have been reset. However, I do not have the airport corruption issue. Anyone know what's going on? I tried to update my battery using the "PB Battery Updater" but that program quits unexpectedly. I'm not sure what else to try...
-
Network Manager Dispatcher with NFS/Autofs
I'm looking to see what is the most recommended method of starting automounted nfs shares after network manager has brought up a wireless connection.
Currently, I'm using the network manager dispatcher and I have dispatch files for:
netfs
autofs
In rc.conf DAEMONS I still have
rpcbind
nfs-common
Should I make dispatcher files for rpcbind and nfs-common as well? What do people around here consider the proper way to do this?Thanks for tip about journalctl!! Made a big difference.
Here is what the script is telling me:
Apr 03 11:45:08 orphan nm-dispatcher.action[553]: Script '/etc/NetworkManager/dispatcher.d/50-mount_sshfs_share_gohilton_2223.sh' took too long; killing it.
I'm guessing the ssh part where it attempts to connect to the remote server and mount the remote ssh is taking to long however even using journalctl in verbose mode really doesn't confirm this assumption.
I'm wondering if this would best be done with systemd unit files? -
Time machine kills Wifi network!!
I had recently posted a thread on TC forum "Weird shut down of TC" that my TC just shuts down routinely.
I have a 1TB TC that has been working very well. I bought the new unibody MBP and the Time machine has been backing up quite nicely for past one month.
I now have a problem that the TM aborts with a message the the drive could not be accessed due to network problems.
My Wifi would be down, status light amber, after a while the status light would go off completely but the disk in TC would be spinning as can feel the spin vibrations. This would happen about every 45 minutes and only way to go back up was to unplug and plug.
I now find that the culprit is time machine. This is what I tried sequentially:
A. Rolled back to 7.3.1 firmware. Same problem.
B. Switched off the TM from prefrences. It worked well for a day.
C. Switched on the TM. As soon as TM backup started, I had the TC wifi freeze.
D. updated to firmware 7.3.2 with TM turned on. Same problem
E. Turned off the airport card, plugged in ethernet cable so now was not using the wifi but wired connection to the TC. Started the TM and again. SAME PROBLEM.
F. Turned off TM, all was well for the entire day.
G. Turned it back on and on the first back up attempt, the WiFi was killed again.
I think now the problem may be with the size of the back up that TM is attempting. It does the 'prepare for back up' pretty quickly but once the back up starts, it kills the WiFi and aborts with a message that there is no network.
Anyone have any idea if I should troubleshoot differently or diagnose this differently?
Has anyone had a problem with TM with large back ups?Hi Alexandre,
Thanks for the input. Sorry my profile was not updated. I am using MBPro 10.5.5.
Here is the output from console which I think is the portion till the network went down. Could not find a way to attach the file.
Thanks for any help you can give:
Dec 7 08:50:36 Mehers-MB-Pro-2 kernel[0]: AFPSleepWakeHandler: waking up
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: Computer did wake up from sleep. Reschedule our timers!
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBack Engine MaxBackEngineController-- MoreSecCopyHelperToolURLAndCheckBundled #1
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- calling MoreSecExecuteRequestInHelperTool
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- back from MoreSecExecuteRequestInHelperTool
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBack Engine MaxBackEngineController-- MoreSecCopyHelperToolURLAndCheckBundled #1
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- calling MoreSecExecuteRequestInHelperTool
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- back from MoreSecExecuteRequestInHelperTool
Dec 7 08:50:40 Mehers-MB-Pro-2 configd[14]: AppleTalk startup complete
Dec 7 09:26:38 Mehers-MB-Pro-2 ntpd[27]: time reset -0.527369 s
Dec 7 09:34:27 Mehers-MB-Pro-2 SyncServer[3340]: SyncServer: Truth vacuumed. Next vacuum date 2008-12-21 09:34:24 +0500
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backup requested by user
Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Starting standard backup
Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Network mountpoint /Volumes/Data-1 not owned by backupd... remounting
Dec 7 09:51:34 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3360
Dec 7 09:51:34 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Network volume mounted at: /Volumes/Data
Dec 7 09:51:36 Mehers-MB-Pro-2 hdiejectd[3374]: running
Dec 7 09:51:37 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: replay_journal: from: 75690496 to: 75768832 (joffset 0x1d0f000)
Dec 7 09:51:38 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: journal replay done.
Dec 7 09:51:38 Mehers-MB-Pro-2 fseventsd[44]: event logs in /Volumes/Backup of Meher’s MB Pro/.fseventsd out of sync with volume. destroying old logs. (524 2 54320)
Dec 7 09:51:38 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Disk image /Volumes/Data/Meher’s MB Pro_002332b0b0ea.sparsebundle mounted at: /Volumes/Backup of Meher’s MB Pro
Dec 7 09:51:38 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backing up to: /Volumes/Backup of Meher’s MB Pro/Backups.backupdb
Dec 7 09:51:38 Mehers-MB-Pro-2 fseventsd[44]: log dir: /Volumes/Backup of Meher’s MB Pro/.fseventsd getting new uuid: 2EF5457F-ED49-4E27-A818-A80F61BCCB86
Dec 7 09:51:47 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (906 > 0)
Dec 7 09:51:52: --- last message repeated 1 time ---
Dec 7 09:52:02 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
Dec 7 09:52:17: --- last message repeated 1 time ---
Dec 7 09:52:37 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: AirPort: No beacon for too long time
Dec 7 09:52:51 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown
Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Down on en1
Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 7 09:52:51: --- last message repeated 1 time ---
Dec 7 09:52:51 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown complete
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x9d22100
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: filter detached
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: down
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: detached
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x9d22100.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x9d22100
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e6:2a:6e
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: got dev 0x5d1be04
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: up
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: attached
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x9d22100.
Dec 7 09:52:55 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
Dec 7 09:53:02 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
Dec 7 09:53:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_Reconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Data
Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: No Ack
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:17 Mehers-MB-Pro-2 configd[14]: AppleTalk startup
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: MAC AUTH succeeded
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Up on en1
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x4fd2300
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: filter detached
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: down
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: detached
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x7c92a00.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x7c92a00
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e6:74:89
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: got dev 0x4dd6604
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: wireless interface detected.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: up
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: attached
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x7c92a00.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is coming UP
Dec 7 09:53:23 Mehers-MB-Pro-2 configd[14]: AppleTalk startup complete
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data
Dec 7 09:53:28 Mehers-MB-Pro-2 diskimages-helper[3365]: terminating disk1 - image is no longer available
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: rder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: ] [IOType Read] [PBlkNum 722696] [LBlkNum 29801] [FSLogMsgID 1403590549] [FSLogMsgOrder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in copyFileOrFd:write error (6)
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: HFS resolvelink: can't find iNode463676
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in copyFileOrFd:write failed - expected:12017024, actual: 1048576
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28: --- last message repeated 1 time ---
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: [FSLogMsgOrder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Stopping backupd to allow ejection of backup destination disk!
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: 741] [FSLogMsgOrder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in recoverIndex:recover canceled (live.0.)
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28: --- last message repeated 1 time ---
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexCI in ContentIndexUpdateContent:Caught mach exception. Fun Fun Fun.
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexGeneral in bool siwriteBackAndIndex(_SI*, __ContentIndex*, const __CFDictionary*, const __CFDictionary*, db_obj**, const __CFString*, int, bool, bool, bool, __SIUserCtx*, const __CFString*, int32_t, bool):ContentIndexUpdateContent failed
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher’s MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexGeneral in void setAttributes(siset_attrctx*, Boolean, long unsigned int):Couldn't update index.
Dec 7 09:53:28 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:29 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:29 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:29: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Stopping backupd to allow ejection of backup destination disk!
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backup failed with error: 26
Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: close: journal 0x4e8ae08, is invalid. aborting outstanding transactions
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:34 Mehers-MB-Pro-2 com.apple.launchd[1] (com.apple.netauth.sysagent[3360]): Stray process with PGID equal to this dead job: PID 3363 PPID 1 check_afp
Dec 7 09:53:40 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data, flags 0, pid 3414
Dec 7 09:54:36 Mehers-MB-Pro-2 [0x0-0x14014].com.apple.finder[259]: AFPFSMapIDName afpfsMapIDNameFSCTL returned -1, errno: 2
Dec 7 09:54:55: --- last message repeated 7 times ---
Dec 7 09:55:08: --- last message repeated 8 times ---
Dec 7 09:55:12 Mehers-MB-Pro-2 [0x0-0x14014].com.apple.finder[259]: AFPFSMapIDName afpfsMapIDNameFSCTL returned -1, errno: 2
Dec 7 09:55:17: --- last message repeated 7 times ---
Dec 7 09:59:07 Mehers-MB-Pro-2 kernel[0]: Link Up: Ctrl 1140, Adv 0de1-0200, Lpa cde1-2c00 Autoneg capable 1
Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Down on en1
Dec 7 09:59:12 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown
Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 7 09:59:12 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown complete
Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x4fd2300
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: filter detached
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: down
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: detached
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x4fd2300.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x4fd2300
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e1:0f:ab
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: got dev 0x4e3d204
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: up
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: attached
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x4fd2300.
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766270
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766270
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766370
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766370
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766520
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766520
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766622
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766622
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766770
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766770
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767020
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767020
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767273
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767273
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
Dec 7 10:00:54 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Backup requested by user
Dec 7 10:00:54 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Starting standard backup
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
Dec 7 10:01:00 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_Reconnect: posting to KEA EINPROGRESS for /Volumes/Data-1
Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 found 1 filesystem(s) with problem(s)
Dec 7 10:01:00 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
Dec 7 10:01:05 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3441
Dec 7 10:01:05 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
Dec 7 10:01:05 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
Dec 7 10:01:05 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Network volume mounted at: /Volumes/Data
Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:20 Mehers-MB-Pro-2 hdiejectd[3459]: running
Dec 7 10:01:21 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: replay_journal: from: 75768832 to: 76011520 (joffset 0x1d0f000)
Dec 7 10:01:22 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: journal replay done.
Dec 7 10:01:22 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
Dec 7 10:01:22 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
Dec 7 10:01:22 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Disk image /Volumes/Data/Meher’s MB Pro_002332b0b0ea.sparsebundle mounted at: /Volumes/Backup of Meher’s MB Pro
Dec 7 10:01:22 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Backing up to: /Volumes/Backup of Meher’s MB Pro/Backups.backupdb
Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (906 > 0)
Dec 7 10:01:35: --- last message repeated 1 time ---
Dec 7 10:01:38 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 unmounting 1 filesystems
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data-1, flags 524288, pid 40
Dec 7 10:01:39 Mehers-MB-Pro-2 loginwindow[39]: No servers unresponsive
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:45 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
Dec 7 10:02:00: --- last message repeated 1 time ---
Dec 7 10:02:10 Mehers-MB-Pro-2 kernel[0]: Link Down
Dec 7 10:02:10 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: interface en is going DOWN
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x9cd4800
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: filter detached
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: down
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: detached
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x9cd4800.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x9cd4800
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:f4:e9:4f
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: got dev 0x5d1be04
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: up
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: attached
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x9cd4800.
Dec 7 10:02:14 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
Dec 7 10:02:20 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
Dec 7 10:02:45 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: Link Up: Ctrl 1140, Adv 0de1-0200, Lpa cde1-2cff Autoneg capable 1
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x62aeb00
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: filter detached
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: down
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: detached
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x62aeb00.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x62aeb00
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:f5:10:a0
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: got dev 0x4e3d204
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: up
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: attached
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x62aeb00.
Dec 7 10:02:48 Mehers-MB-Pro-2 mDNSResponder[16]: Note: Frequent transitions for interface en0 (192.168.1.130); network traffic reduction measures in effect
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfsCheckOpenFiles: File <1d89> can not be reopened due to deny modes or byte range locks (file has exclusive access).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfsCheckOpenFiles: File <token> can not be reopened due to deny modes or byte range locks (file has exclusive access).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
Dec 7 10:02:55: --- last message repeated 1 time ---
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
Dec 7 10:02:55: --- last message repeated 1 time ---
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
Dec 7 10:02:55: --- last message repeated 1 time ---
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED). -
Mavericks: Killer of Networked Printing
I'm a veteran user of PC/Windows after 2y owning a MBP I'm still amazed at how much stuff just is bizarre in the OSX world that worked flawlessly in the Windows world, at least since Win 7 especially. Very difficult to do the most common tasks used all of the time for me as a somewhat power Windows user, in the OSX world. For example: no way to role back a driver installation or application if it turns out not to be a good thing without an entire blithering Time Machine restore. That, is just too lame! Next comes the very commonly used column header sort feature in Windows Explorer. Just doesn't work nearly as well in OSX world. When I updated to Mavericks, I discovered the very lovely kind of horizontal hourglass display of Safari Top Sites was removed in the latest version, and there is no way to revert back to the prior version. As well, one could swipe thru history pages in the prior version (at least the one assoc w/ Lion) has now been removed and we have an ugly list now and no way to view these pages unless I missed something. Next comes the very very frequently use Screen Print, Home & End buttons in the default Windows keyboard. These features are used very frequently, and yet they don't exist in OSX, at least on my smaller MBP keyboard. Instead, it's a key combination I have a hard time remembering, and it just doens't work quickly and intutively as it does in Win world. These are real productivity features.
Now comes my HP Photosmart D5400 connected to my MSHome network: worked fine prior to Mavericks, now, despite the fact Software Update installed the alledgedly updated driver for X, not happening, for me and what sounds like everything else.
OSX is not the best productivity OS unless you're really an advanced user it would appear. I really do like many features of this MBP, but so many areas are just plain odd in this day an age in terms of practicality and productivity. And a huge one is: no built-in way to role back to prior states w/o restoring from a former image.
I'm hoping if I post here when the soln to network printing (not some blithering work around!) is posted hopefully I can print wirelessly once again. The problem is posted all over the web so I won't go into detail, and don't want to bother w/ other ways of making the broken thing work as a work around. I tried a few of those last evening, killing a good hour+ to no avail. May end up going back to Lion if I can figure out how to restore just the OSX partition from an external TM back up I did early on, taking care to save all my data prior to that. I do like a feature or two in X, but they're not really all that useful in the end.This pretty much sums it up:
Reverting a system backwards from Mavericks is no picnic
Summary: After installing OS X Mavericks to their systems, some users want to go back to whatever system version they had before, usually Mountain Lion or Lion. However, a retrograde is not an easy process.
By David Morgenstern for The Apple Core | November 1, 2013 -- 05:42 GMT (22:42 PDT)
Following an installation of OS X Mavericks to their system, a number of readers have contacted me about retrograding, returning to an older version of the OS. They seem to believe that this is a process similar to the upgrade: simply clicking a few buttons in Time Machine and it will be done. Nothing can be further from the truth.
Man oh man, that is so blithering lame--for 2013!
Maybe you are looking for
-
I have two different itunes music files on my computer. How do I combine them into one file?
I have two different itunes music files on my computer. How do I combine them into one file?
-
RFC error while running sync job in AC 10
I have done all the configuration to add new SAP system via SPRO in GRC 10. Now I am trying to run the sync job for the first time, I am getting the below mssage. I checked the RFC desitinations, it looks fine. Error in RFC; 'Function module "/GRCPI/
-
Can't install iTunes on windows 7 please help!
Been trying to install iTune on Window 7 but every time got message can anyone help please? Thank you
-
Red CIrcle X becaue the printer does not exist
I have been getting the "print - RED CIRCLE X" because the requested printer does not exist" since I installed CS5 when it first came out. I am using Windows VISTA Home Premium, Service Pack 2 - Photoshop CS5, 12.0.4 64 bit. My computer is an i-7, 92
-
At http://www.omt3d.com/sponsors.htm, you'll see the table explodes, as I add text. How do I fix this issue?