Nov 29 15:30:56 nava-TOSHIBA-NB250 kernel: [ 1534.810139] perf samples too long (5022 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
Nov 29 15:32:35 nava-TOSHIBA-NB250 kernel: [ 1633.840108] Bluetooth: hci0 command 0x1403 tx timeout
Nov 29 15:32:37 nava-TOSHIBA-NB250 kernel: [ 1635.844107] Bluetooth: hci0 command 0x0c2d tx timeout
Nov 29 15:46:58 nava-TOSHIBA-NB250 NetworkManager[719]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 15:48:34 nava-TOSHIBA-NB250 kernel: [ 2592.216168] Bluetooth: hci0 command 0x0405 tx timeout
Nov 29 15:48:54 nava-TOSHIBA-NB250 kernel: [ 2612.069688] perf samples too long (10083 > 10000), lowering kernel.perf_event_max_sample_rate to 12500
Nov 29 15:49:14 nava-TOSHIBA-NB250 kernel: [ 2632.380120] Bluetooth: hci0 command 0x0408 tx timeout
Nov 29 16:00:47 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 192.168.1.1 port 67 (xid=0x6b745fff)
Nov 29 16:00:47 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 29 16:00:47 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 3311 seconds.
Nov 29 16:00:47 nava-TOSHIBA-NB250 NetworkManager[719]: <info> (wlan0): DHCPv4 state changed bound -> renew
Nov 29 16:00:47 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   address 192.168.1.101
Nov 29 16:00:47 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   prefix 24 (255.255.255.0)
Nov 29 16:00:47 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   gateway 192.168.1.1
Nov 29 16:00:47 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   nameserver '192.168.2.1'
Nov 29 16:00:47 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   nameserver '192.168.1.1'
Nov 29 16:18:58 nava-TOSHIBA-NB250 NetworkManager[719]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 16:26:58 nava-TOSHIBA-NB250 NetworkManager[719]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 16:34:58 nava-TOSHIBA-NB250 NetworkManager[719]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 16:52:18 nava-TOSHIBA-NB250 NetworkManager[719]: <info> kernel firmware directory '/lib/firmware' changed
Nov 29 16:55:33 nava-TOSHIBA-NB250 kernel: [ 6611.232611] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 29 16:55:38 nava-TOSHIBA-NB250 kernel: [ 6616.594631] type=1400 audit(1385740538.815:47): apparmor="STATUS" operation="profile_replace" parent=5162 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=5166 comm="apparmor_parser"
Nov 29 16:55:38 nava-TOSHIBA-NB250 kernel: [ 6616.599473] type=1400 audit(1385740538.819:48): apparmor="STATUS" operation="profile_replace" parent=5162 profile="unconfined" name="/usr/sbin/cupsd" pid=5166 comm="apparmor_parser"
Nov 29 16:55:39 nava-TOSHIBA-NB250 kernel: [ 6617.042574] type=1400 audit(1385740539.263:49): apparmor="STATUS" operation="profile_replace" parent=5216 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=5220 comm="apparmor_parser"
Nov 29 16:55:39 nava-TOSHIBA-NB250 kernel: [ 6617.042634] type=1400 audit(1385740539.263:50): apparmor="STATUS" operation="profile_replace" parent=5216 profile="unconfined" name="/usr/sbin/cupsd" pid=5220 comm="apparmor_parser"
Nov 29 16:55:39 nava-TOSHIBA-NB250 kernel: [ 6617.047887] type=1400 audit(1385740539.267:51): apparmor="STATUS" operation="profile_replace" parent=5216 profile="unconfined" name="/usr/sbin/cupsd" pid=5220 comm="apparmor_parser"
Nov 29 16:55:58 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 192.168.1.1 port 67 (xid=0x6b745fff)
Nov 29 16:55:58 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 29 16:55:58 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 3248 seconds.
Nov 29 16:55:58 nava-TOSHIBA-NB250 NetworkManager[719]: <info> (wlan0): DHCPv4 state changed renew -> renew
Nov 29 16:55:58 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   address 192.168.1.101
Nov 29 16:55:58 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   prefix 24 (255.255.255.0)
Nov 29 16:55:58 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   gateway 192.168.1.1
Nov 29 16:55:58 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   nameserver '192.168.2.1'
Nov 29 16:55:58 nava-TOSHIBA-NB250 NetworkManager[719]: <info>   nameserver '192.168.1.1'
Nov 29 16:57:40 nava-TOSHIBA-NB250 kernel: [ 6737.955732] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov 29 16:57:40 nava-TOSHIBA-NB250 kernel: [ 6738.128613] JFS: nTxBlock = 8192, nTxLock = 65536
Nov 29 16:57:40 nava-TOSHIBA-NB250 kernel: [ 6738.326457] NTFS driver 2.1.30 [Flags: R/O MODULE].
Nov 29 16:57:40 nava-TOSHIBA-NB250 kernel: [ 6738.693181] QNX4 filesystem 0.2.3 registered.
Nov 29 16:57:40 nava-TOSHIBA-NB250 kernel: [ 6738.770761] xor: measuring software checksum speed
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6738.808065]    pIII_sse  :  2204.000 MB/sec
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6738.848079]    prefetch64-sse:  2421.000 MB/sec
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6738.848090] xor: using function: prefetch64-sse (2421.000 MB/sec)
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6738.936758] raid6: mmxx1      116 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.004133] raid6: mmxx2      244 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.073788] raid6: sse1x1      23 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.141308] raid6: sse1x2      45 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.208906] raid6: sse2x1      45 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.276580] raid6: sse2x2      90 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.344826] raid6: int32x1     63 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.412967] raid6: int32x2     79 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.480389] raid6: int32x4     78 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.548332] raid6: int32x8     98 MB/s
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.548364] raid6: using algorithm mmxx2 (244 MB/s)
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.548373] raid6: using ssse3x1 recovery algorithm
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.614888] bio: create slab <bio-1> at 1
Nov 29 16:57:41 nava-TOSHIBA-NB250 kernel: [ 6739.630169] Btrfs loaded
Nov 29 16:58:02 nava-TOSHIBA-NB250 kernel: [ 6760.467596] type=1400 audit(1385740682.688:52): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/sbin/dhclient" pid=12055 comm="apparmor_parser"
Nov 29 16:58:02 nava-TOSHIBA-NB250 kernel: [ 6760.470398] type=1400 audit(1385740682.692:53): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=12055 comm="apparmor_parser"
Nov 29 16:58:02 nava-TOSHIBA-NB250 kernel: [ 6760.472382] type=1400 audit(1385740682.696:54): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=12055 comm="apparmor_parser"
Nov 29 16:58:03 nava-TOSHIBA-NB250 kernel: [ 6760.783027] type=1400 audit(1385740683.004:55): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=12054 comm="apparmor_parser"
Nov 29 16:58:03 nava-TOSHIBA-NB250 kernel: [ 6760.800849] type=1400 audit(1385740683.024:56): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="chromium_browser" pid=12054 comm="apparmor_parser"
Nov 29 16:58:10 nava-TOSHIBA-NB250 kernel: [ 6768.427213] type=1400 audit(1385740690.648:57): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=12058 comm="apparmor_parser"
Nov 29 16:58:10 nava-TOSHIBA-NB250 kernel: [ 6768.443808] type=1400 audit(1385740690.664:58): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/sbin/cupsd" pid=12058 comm="apparmor_parser"
Nov 29 16:58:15 nava-TOSHIBA-NB250 kernel: [ 6773.005296] type=1400 audit(1385740695.228:59): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/sbin/ntpd" pid=12074 comm="apparmor_parser"
Nov 29 16:58:18 nava-TOSHIBA-NB250 kernel: [ 6775.937857] type=1400 audit(1385740698.160:60): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/sbin/tcpdump" pid=12080 comm="apparmor_parser"
Nov 29 16:59:09 nava-TOSHIBA-NB250 kernel: [ 6826.879151] type=1400 audit(1385740749.099:61): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/bin/evince" pid=12056 comm="apparmor_parser"
Nov 29 16:59:09 nava-TOSHIBA-NB250 kernel: [ 6826.909349] type=1400 audit(1385740749.131:62): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="sanitized_helper" pid=12056 comm="apparmor_parser"
Nov 29 16:59:09 nava-TOSHIBA-NB250 kernel: [ 6826.940146] type=1400 audit(1385740749.163:63): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/bin/evince-previewer" pid=12056 comm="apparmor_parser"
Nov 29 16:59:09 nava-TOSHIBA-NB250 kernel: [ 6826.966353] type=1400 audit(1385740749.187:64): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="sanitized_helper" pid=12056 comm="apparmor_parser"
Nov 29 16:59:09 nava-TOSHIBA-NB250 kernel: [ 6826.983639] type=1400 audit(1385740749.203:65): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="/usr/bin/evince-thumbnailer" pid=12056 comm="apparmor_parser"
Nov 29 16:59:09 nava-TOSHIBA-NB250 kernel: [ 6827.001062] type=1400 audit(1385740749.223:66): apparmor="STATUS" operation="profile_replace" parent=12049 profile="unconfined" name="sanitized_helper" pid=12056 comm="apparmor_parser"
Nov 29 16:59:14 nava-TOSHIBA-NB250 kernel: [ 6832.535855] type=1400 audit(1385740754.755:67): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/sbin/dhclient" pid=12158 comm="apparmor_parser"
Nov 29 16:59:14 nava-TOSHIBA-NB250 kernel: [ 6832.539009] type=1400 audit(1385740754.759:68): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=12158 comm="apparmor_parser"
Nov 29 16:59:14 nava-TOSHIBA-NB250 kernel: [ 6832.541554] type=1400 audit(1385740754.763:69): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=12158 comm="apparmor_parser"
Nov 29 16:59:15 nava-TOSHIBA-NB250 kernel: [ 6833.175652] type=1400 audit(1385740755.395:70): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=12157 comm="apparmor_parser"
Nov 29 16:59:15 nava-TOSHIBA-NB250 kernel: [ 6833.189264] type=1400 audit(1385740755.411:71): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="chromium_browser" pid=12157 comm="apparmor_parser"
Nov 29 16:59:22 nava-TOSHIBA-NB250 kernel: [ 6840.233945] type=1400 audit(1385740762.455:72): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=12161 comm="apparmor_parser"
Nov 29 16:59:22 nava-TOSHIBA-NB250 kernel: [ 6840.241775] type=1400 audit(1385740762.463:73): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/sbin/cupsd" pid=12161 comm="apparmor_parser"
Nov 29 16:59:24 nava-TOSHIBA-NB250 kernel: [ 6842.370567] type=1400 audit(1385740764.591:74): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/sbin/ntpd" pid=12167 comm="apparmor_parser"
Nov 29 16:59:26 nava-TOSHIBA-NB250 kernel: [ 6844.637358] type=1400 audit(1385740766.859:75): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/sbin/tcpdump" pid=12169 comm="apparmor_parser"
Nov 29 16:59:34 nava-TOSHIBA-NB250 kernel: [ 6852.468246] usb 5-2: new full-speed USB device number 6 using uhci_hcd
Nov 29 16:59:34 nava-TOSHIBA-NB250 kernel: [ 6852.588122] usb 5-2: device descriptor read/64, error -71
Nov 29 16:59:35 nava-TOSHIBA-NB250 kernel: [ 6852.812227] usb 5-2: device descriptor read/64, error -71
Nov 29 16:59:35 nava-TOSHIBA-NB250 kernel: [ 6853.028198] usb 5-2: new full-speed USB device number 7 using uhci_hcd
Nov 29 16:59:35 nava-TOSHIBA-NB250 kernel: [ 6853.148230] usb 5-2: device descriptor read/64, error -71
Nov 29 16:59:35 nava-TOSHIBA-NB250 kernel: [ 6853.372215] usb 5-2: device descriptor read/64, error -71
Nov 29 16:59:35 nava-TOSHIBA-NB250 kernel: [ 6853.588205] usb 5-2: new full-speed USB device number 8 using uhci_hcd
Nov 29 16:59:36 nava-TOSHIBA-NB250 kernel: [ 6854.004179] usb 5-2: device not accepting address 8, error -71
Nov 29 16:59:36 nava-TOSHIBA-NB250 kernel: [ 6854.116216] usb 5-2: new full-speed USB device number 9 using uhci_hcd
Nov 29 16:59:36 nava-TOSHIBA-NB250 kernel: [ 6854.528163] usb 5-2: device not accepting address 9, error -71
Nov 29 16:59:36 nava-TOSHIBA-NB250 kernel: [ 6854.528278] hub 5-0:1.0: unable to enumerate USB device on port 2
Nov 29 17:00:18 nava-TOSHIBA-NB250 kernel: [ 6895.947397] type=1400 audit(1385740818.166:76): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/bin/evince" pid=12159 comm="apparmor_parser"
Nov 29 17:00:18 nava-TOSHIBA-NB250 kernel: [ 6895.973100] type=1400 audit(1385740818.194:77): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="sanitized_helper" pid=12159 comm="apparmor_parser"
Nov 29 17:00:18 nava-TOSHIBA-NB250 kernel: [ 6895.990043] type=1400 audit(1385740818.210:78): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/bin/evince-previewer" pid=12159 comm="apparmor_parser"
Nov 29 17:00:18 nava-TOSHIBA-NB250 kernel: [ 6896.002740] type=1400 audit(1385740818.222:79): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="sanitized_helper" pid=12159 comm="apparmor_parser"
Nov 29 17:00:18 nava-TOSHIBA-NB250 kernel: [ 6896.016699] type=1400 audit(1385740818.238:80): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="/usr/bin/evince-thumbnailer" pid=12159 comm="apparmor_parser"
Nov 29 17:00:18 nava-TOSHIBA-NB250 kernel: [ 6896.026522] type=1400 audit(1385740818.246:81): apparmor="STATUS" operation="profile_replace" parent=12152 profile="unconfined" name="sanitized_helper" pid=12159 comm="apparmor_parser"
Nov 29 17:08:58 nava-TOSHIBA-NB250 NetworkManager[719]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Linux version 3.11.0-13-generic (buildd@aatxe) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) ) #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013 (Ubuntu 3.11.0-13.20-generic 3.11.6)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] KERNEL supported cpus:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   Intel GenuineIntel
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   AMD AuthenticAMD
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   NSC Geode by NSC
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   Cyrix CyrixInstead
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   Centaur CentaurHauls
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   Transmeta GenuineTMx86
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   Transmeta TransmetaCPU
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   UMC UMC UMC UMC
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009dbff] usable
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009dc00-0x000000000009ffff] reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000dc000-0x00000000000dffff] reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e4000-0x00000000000fffff] reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007f5cffff] usable
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x000000007f5d0000-0x000000007f5dffff] ACPI data
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x000000007f5e0000-0x000000007f5e2fff] ACPI NVS
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x000000007f5e3000-0x000000007fffffff] reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] SMBIOS 2.5 present.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] DMI: TOSHIBA TOSHIBA NB250/PAV10 DDR3, BIOS V1.60 07/30/2010
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: last_pfn = 0x7f5d0 max_arch_pfn = 0x1000000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] MTRR default type: uncachable
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   00000-9FFFF write-back
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   C0000-CFFFF write-protect
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   D0000-DFFFF uncachable
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   E0000-FFFFF write-protect
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] MTRR variable ranges enabled:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   0 base 000000000 mask 080000000 write-back
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   1 base 07F600000 mask 0FFE00000 uncachable
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   2 base 07F800000 mask 0FF800000 uncachable
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   3 disabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   4 disabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   5 disabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   6 disabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   7 disabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] original variable MTRRs
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 0, base: 0GB, range: 2GB, type WB
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 1, base: 2038MB, range: 2MB, type UC
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 2, base: 2040MB, range: 8MB, type UC
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] total RAM covered: 2038M
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Found optimal setting for mtrr clean up
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 16M 	num_reg: 3  	lose cover RAM: 0G
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] New variable MTRRs
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 0, base: 0GB, range: 2GB, type WB
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 1, base: 2038MB, range: 2MB, type UC
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 2, base: 2040MB, range: 8MB, type UC
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] found SMP MP-table at [mem 0x000f7d30-0x000f7d3f] mapped at [c00f7d30]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] initial memory mapped: [mem 0x00000000-0x01ffffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Base memory trampoline at [c0099000] 99000 size 16384
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x37800000-0x379fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x37800000-0x379fffff] page 2M
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x34000000-0x377fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x34000000-0x377fffff] page 2M
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x33ffffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x00200000-0x33ffffff] page 2M
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x37a00000-0x37bfdfff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x37a00000-0x37bfdfff] page 4k
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BRK [0x01b39000, 0x01b39fff] PGTABLE
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] RAMDISK: [mem 0x35fa0000-0x36fc7fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: RSDP 000f7c90 00024 (v02 TOSCPL)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: XSDT 7f5d7ae1 00074 (v01 TOSCPL TOSCPL00 06040000  LTP 00000000)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: FACP 7f5dfc60 000F4 (v03 TOSCPL TOSCPL00 06040000 PTL  00000002)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: DSDT 7f5d8c77 06F75 (v01 TOSCPL TOSCPL00 06040000 MSFT 03000000)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: FACS 7f5e2fc0 00040
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: TCPA 7f5dfd54 00032 (v01 Phoeni  x       06040000  TL  00000000)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: HPET 7f5dfd86 00038 (v01 DELL   M09      06040000 LOHR 0000005A)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: MCFG 7f5dfdbe 0003C (v01 INTEL  CRESTLNE 06040000 LOHR 0000005A)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: SLIC 7f5dfdfa 00176 (v01 TOSCPL TOSCPL00 06040000 LOHR 00000000)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: APIC 7f5dff70 00068 (v01 TOSCPL TOSCPL00 06040000  LTP 00000000)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: BOOT 7f5dffd8 00028 (v01 TOSCPL TOSCPL00 06040000  LTP 00000001)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: SSDT 7f5d80d7 0025F (v01  PmRef  Cpu0Tst 00003000 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: SSDT 7f5d8031 000A6 (v01  PmRef  Cpu1Tst 00003000 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: SSDT 7f5d7b55 004DC (v02  PmRef    CpuPm 00003000 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] 1145MB HIGHMEM available.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] 891MB LOWMEM available.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   mapped low ram: 0 - 37bfe000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   low ram: 0 - 37bfe000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] BRK [0x01b3a000, 0x01b3afff] PGTABLE
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Zone ranges:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   Normal   [mem 0x01000000-0x37bfdfff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   HighMem  [mem 0x37bfe000-0x7f5cffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Movable zone start for each node
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Early memory node ranges
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009cfff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   node   0: [mem 0x00100000-0x7f5cffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] On node 0 totalpages: 521580
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] free_area_init_node: node 0, pgdat c1948b40, node_mem_map f4fb0020
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   DMA zone: 32 pages used for memmap
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   DMA zone: 0 pages reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   DMA zone: 3996 pages, LIFO batch:0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   Normal zone: 1752 pages used for memmap
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   Normal zone: 224254 pages, LIFO batch:31
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   HighMem zone: 2292 pages used for memmap
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]   HighMem zone: 293330 pages, LIFO batch:31
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Using APIC driver default
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x1008
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] nr_irqs_gsi: 40
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dbfff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000dc000-0x000dffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000e3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e4000-0x000fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: [mem 0x80000000-0xdfffffff] available for PCI devices
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] PERCPU: Embedded 14 pages/cpu @f7bd6000 s36288 r0 d21056 u57344
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] pcpu-alloc: s36288 r0 d21056 u57344 alloc=14*4096
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 519796
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=dae33f41-73b2-4804-9829-e92a660ae9ad ro quiet splash vt.handoff=7
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing CPU#0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] allocated 4173432 bytes of page_cgroup
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing HighMem for node 0 (00037bfe:0007f5d0)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Memory: 2036848K/2086320K available (6352K kernel code, 607K rwdata, 2640K rodata, 880K init, 908K bss, 49472K reserved, 1173320K highmem)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] virtual kernel memory layout:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]     fixmap  : 0xfff14000 - 0xfffff000   ( 940 kB)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]     pkmap   : 0xffc00000 - 0xffe00000   (2048 kB)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]     vmalloc : 0xf83fe000 - 0xffbfe000   ( 120 MB)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xf7bfe000   ( 891 MB)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]       .init : 0xc1962000 - 0xc1a3e000   ( 880 kB)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]       .data : 0xc16343a4 - 0xc1961dc0   (3254 kB)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000]       .text : 0xc1000000 - 0xc16343a4   (6352 kB)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Hierarchical RCU implementation.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] NR_IRQS:2304 nr_irqs:512 16
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] CPU 0 irqstacks, hard=f7008000 soft=f700a000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] Console: colour dummy device 80x25
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] console [tty0] enabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] hpet clockevent registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.000000] tsc: Detected 1662.333 MHz processor
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004003] Calibrating delay loop (skipped), value calculated using timer frequency.. 3324.66 BogoMIPS (lpj=6649332)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004012] pid_max: default: 32768 minimum: 301
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004087] Security Framework initialized
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004117] AppArmor: AppArmor initialized
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004122] Yama: becoming mindful.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004231] Mount-cache hash table entries: 512
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004657] Initializing cgroup subsys memory
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004680] Initializing cgroup subsys devices
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004686] Initializing cgroup subsys freezer
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004691] Initializing cgroup subsys blkio
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004696] Initializing cgroup subsys perf_event
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004704] Initializing cgroup subsys hugetlb
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004755] CPU: Physical Processor ID: 0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004760] CPU: Processor Core ID: 0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004766] mce: CPU supports 5 MCE banks
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004780] CPU0: Thermal monitoring handled by SMI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004803] Last level iTLB entries: 4KB 32, 2MB 0, 4MB 0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004803] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 8
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004803] tlb_flushall_shift: 6
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.005218] Freeing SMP alternatives memory: 28K (c1a3e000 - c1a45000)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.009280] ACPI: Core revision 20130517
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.019421] ACPI: All ACPI Tables successfully acquired
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.020023] ftrace: allocating 27140 entries in 54 pages
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.040166] Enabling APIC mode:  Flat.  Using 1 I/O APICs
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.040604] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.083743] smpboot: CPU0: Intel(R) Atom(TM) CPU N455   @ 1.66GHz (fam: 06, model: 1c, stepping: 0a)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084000] Performance Events: PEBS fmt0+, 8-deep LBR, Atom events, Intel PMU driver.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084000] ... version:                3
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084000] ... bit width:              40
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084000] ... generic registers:      2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084000] ... value mask:             000000ffffffffff
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084000] ... max period:             000000007fffffff
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084000] ... fixed-purpose events:   3
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084000] ... event mask:             0000000700000003
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084222] CPU 1 irqstacks, hard=f70f0000 soft=f70f2000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.084230] smpboot: Booting Node   0, Processors  #1 OK
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004000] Initializing CPU#1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.004000] CPU0: Thermal monitoring enabled (TM1)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104000] TSC synchronization [CPU#0 -> CPU#1]:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104000] Measured 3464967086 cycles TSC warp between CPUs, turning off TSC clock.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104000] tsc: Marking TSC unstable due to check_tsc_sync_source failed
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104119] Brought up 2 CPUs
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104126] smpboot: Total of 2 processors activated (6649.33 BogoMIPS)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104252] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104857] devtmpfs: initialized
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104857] EVM: security.selinux
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104857] EVM: security.SMACK64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104857] EVM: security.capability
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.104857] PM: Registering ACPI NVS region [mem 0x7f5e0000-0x7f5e2fff] (12288 bytes)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.108907] regulator-dummy: no parameters
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.108963] RTC time: 17:17:22, date: 11/29/13
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.109064] NET: Registered protocol family 16
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.109417] EISA bus registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.109568] ACPI: bus type PCI registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.109575] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.109705] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.109714] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.109718] PCI: Using MMCONFIG for extended config space
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.109722] PCI: Using configuration type 1 for base access
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.112208] bio: create slab <bio-0> at 0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.112228] ACPI: Added _OSI(Module Device)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.112236] ACPI: Added _OSI(Processor Device)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.112241] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.112246] ACPI: Added _OSI(Processor Aggregator Device)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.115249] ACPI: EC: Look up EC in DSDT
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.124864] ACPI: SSDT 7f5d89a0 00203 (v02  PmRef  Cpu0Ist 00003000 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.125634] ACPI: Dynamic OEM Table Load:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.125642] ACPI: SSDT   (null) 00203 (v02  PmRef  Cpu0Ist 00003000 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.125936] ACPI: SSDT 7f5d8336 005E5 (v02  PmRef  Cpu0Cst 00003001 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.126648] ACPI: Dynamic OEM Table Load:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.126654] ACPI: SSDT   (null) 005E5 (v02  PmRef  Cpu0Cst 00003001 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.127205] ACPI: SSDT 7f5d8ba3 000D4 (v02  PmRef  Cpu1Ist 00003000 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.127941] ACPI: Dynamic OEM Table Load:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.127948] ACPI: SSDT   (null) 000D4 (v02  PmRef  Cpu1Ist 00003000 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.128138] ACPI: SSDT 7f5d891b 00085 (v02  PmRef  Cpu1Cst 00003000 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.128853] ACPI: Dynamic OEM Table Load:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.128860] ACPI: SSDT   (null) 00085 (v02  PmRef  Cpu1Cst 00003000 INTL 20050624)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.132054] ACPI: Interpreter enabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.132073] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130517/hwxface-571)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.132084] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.132118] ACPI: (supports S0 S3 S4 S5)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.132123] ACPI: Using IOAPIC for interrupt routing
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.132190] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.132436] ACPI: No dock devices found.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.204732] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.204897] ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20130517/dsfield-211)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.204912] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f70282a0), AE_ALREADY_EXISTS (20130517/psparse-536)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.204931] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.205101] ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20130517/dsfield-211)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.205115] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f70282a0), AE_ALREADY_EXISTS (20130517/psparse-536)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.205141] acpi PNP0A08:00: ACPI _OSC support notification failed, disabling PCIe ASPM
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.205148] acpi PNP0A08:00: Unable to request _OSC control (_OSC support mask: 0x08)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208423] PCI host bridge to bus 0000:00
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208434] pci_bus 0000:00: root bus resource [bus 00-3f]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208441] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208448] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208454] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208461] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208467] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208473] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208480] pci_bus 0000:00: root bus resource [mem 0x80000000-0xf7ffffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208486] pci_bus 0000:00: root bus resource [io  0x0d00-0xfdff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208508] pci 0000:00:00.0: [8086:a010] type 00 class 0x060000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208709] pci 0000:00:02.0: [8086:a011] type 00 class 0x030000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208729] pci 0000:00:02.0: reg 0x10: [mem 0xf0200000-0xf027ffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208741] pci 0000:00:02.0: reg 0x14: [io  0x18d0-0x18d7]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208752] pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208763] pci 0000:00:02.0: reg 0x1c: [mem 0xf0000000-0xf00fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208959] pci 0000:00:02.1: [8086:a012] type 00 class 0x038000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.208976] pci 0000:00:02.1: reg 0x10: [mem 0xf0280000-0xf02fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.209225] pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.209254] pci 0000:00:1b.0: reg 0x10: [mem 0xf0300000-0xf0303fff 64bit]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.209351] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.209536] pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.209638] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.209753] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.209843] pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.209947] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.210066] pci 0000:00:1c.1: System wakeup disabled by ACPI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.210156] pci 0000:00:1c.2: [8086:27d4] type 01 class 0x060400
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.210258] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.210451] pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.210512] pci 0000:00:1d.0: reg 0x20: [io  0x1820-0x183f]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.210687] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.210774] pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.210836] pci 0000:00:1d.1: reg 0x20: [io  0x1840-0x185f]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.210971] pci 0000:00:1d.1: System wakeup disabled by ACPI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211058] pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211121] pci 0000:00:1d.2: reg 0x20: [io  0x1860-0x187f]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211287] pci 0000:00:1d.2: System wakeup disabled by ACPI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211379] pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211439] pci 0000:00:1d.3: reg 0x20: [io  0x1880-0x189f]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211571] pci 0000:00:1d.3: System wakeup disabled by ACPI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211669] pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211703] pci 0000:00:1d.7: reg 0x10: [mem 0xf0504000-0xf05043ff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211825] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.211957] pci 0000:00:1d.7: System wakeup disabled by ACPI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212066] pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212237] pci 0000:00:1e.0: System wakeup disabled by ACPI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212335] pci 0000:00:1f.0: [8086:27bc] type 00 class 0x060100
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212443] pci 0000:00:1f.0: [Firmware Bug]: TigerPoint LPC.BM_STS cleared
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212648] pci 0000:00:1f.2: [8086:27c1] type 00 class 0x010601
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212675] pci 0000:00:1f.2: reg 0x10: [io  0x18e8-0x18ef]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212690] pci 0000:00:1f.2: reg 0x14: [io  0x18dc-0x18df]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212705] pci 0000:00:1f.2: reg 0x18: [io  0x18e0-0x18e7]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212719] pci 0000:00:1f.2: reg 0x1c: [io  0x18d8-0x18db]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212733] pci 0000:00:1f.2: reg 0x20: [io  0x18c0-0x18cf]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212748] pci 0000:00:1f.2: reg 0x24: [mem 0xf0504400-0xf05047ff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212803] pci 0000:00:1f.2: PME# supported from D3hot
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.212983] pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.213057] pci 0000:00:1f.3: reg 0x20: [io  0x18a0-0x18bf]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.213369] pci 0000:00:1c.0: PCI bridge to [bus 05]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.213380] pci 0000:00:1c.0:   bridge window [io  0x0000-0x0fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.213537] pci 0000:07:00.0: [168c:002b] type 00 class 0x028000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.213577] pci 0000:07:00.0: reg 0x10: [mem 0xf0100000-0xf010ffff 64bit]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.213719] pci 0000:07:00.0: supports D1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.213725] pci 0000:07:00.0: PME# supported from D0 D1 D3hot
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220038] pci 0000:00:1c.1: PCI bridge to [bus 07]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220051] pci 0000:00:1c.1:   bridge window [mem 0xf0100000-0xf01fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220264] pci 0000:09:00.0: [10ec:8136] type 00 class 0x020000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220334] pci 0000:09:00.0: reg 0x10: [io  0x2000-0x20ff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220454] pci 0000:09:00.0: reg 0x18: [mem 0xf050c000-0xf050cfff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220527] pci 0000:09:00.0: reg 0x20: [mem 0xf0508000-0xf050bfff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220786] pci 0000:09:00.0: supports D1 D2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220793] pci 0000:09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220053] pci 0000:09:00.0: System wakeup disabled by ACPI
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220243] pci 0000:00:1c.2: PCI bridge to [bus 09]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220254] pci 0000:00:1c.2:   bridge window [io  0x2000-0x2fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220268] pci 0000:00:1c.2:   bridge window [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220404] pci 0000:00:1e.0: PCI bridge to [bus 11] (subtractive decode)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220421] pci 0000:00:1e.0:   bridge window [io  0x0000-0x0cf7] (subtractive decode)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220428] pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220434] pci 0000:00:1e.0:   bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220441] pci 0000:00:1e.0:   bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220447] pci 0000:00:1e.0:   bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220454] pci 0000:00:1e.0:   bridge window [mem 0x000e0000-0x000e3fff] (subtractive decode)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220461] pci 0000:00:1e.0:   bridge window [mem 0x80000000-0xf7ffffff] (subtractive decode)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220467] pci 0000:00:1e.0:   bridge window [io  0x0d00-0xfdff] (subtractive decode)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.220497] pci_bus 0000:00: on NUMA node 0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.240187] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 12 14 15)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.240358] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.240524] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.240689] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.240862] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.241038] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.241218] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.241392] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242059] ACPI: Enabled 2 GPEs in block 00 to 1F
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242080] ACPI: \_SB_.PCI0: notify handler is installed
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242189] Found 1 acpi root devices
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242286] ACPI: EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] vgaarb: loaded
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] vgaarb: bridge control possible 0000:00:02.0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] SCSI subsystem initialized
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] ACPI: bus type ATA registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] libata version 3.00 loaded.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] ACPI: bus type USB registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] usbcore: registered new interface driver usbfs
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] usbcore: registered new interface driver hub
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] usbcore: registered new device driver usb
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.242497] PCI: Using ACPI for IRQ routing
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.250945] PCI: pci_cache_line_size set to 64 bytes
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.250997] pci 0000:00:1d.7: address space collision: [mem 0xf0504000-0xf05043ff] conflicts with PCI Bus 0000:09 [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251016] pci 0000:00:1f.2: address space collision: [mem 0xf0504400-0xf05047ff] conflicts with PCI Bus 0000:09 [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251058] e820: reserve RAM buffer [mem 0x0009dc00-0x0009ffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251065] e820: reserve RAM buffer [mem 0x7f5d0000-0x7fffffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251304] NetLabel: Initializing
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251310] NetLabel:  domain hash size = 128
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251313] NetLabel:  protocols = UNLABELED CIPSOv4
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251336] NetLabel:  unlabeled traffic allowed by default
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251380] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251380] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.251380] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.253040] Switched to clocksource hpet
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267130] AppArmor: AppArmor Filesystem Enabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267202] pnp: PnP ACPI init
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267239] ACPI: bus type PNP registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267725] system 00:00: [io  0x0800-0x080f] has been reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267736] system 00:00: [io  0x1000-0x107f] could not be reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267744] system 00:00: [io  0x1180-0x11bf] has been reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267751] system 00:00: [io  0x04d0-0x04d1] has been reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267758] system 00:00: [io  0xfe00] has been reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267765] system 00:00: [io  0x164e-0x174c] has been reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267774] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267782] system 00:00: [mem 0xfed14000-0xfed17fff] has been reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267789] system 00:00: [mem 0xf8000000-0xfbffffff] has been reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267797] system 00:00: [mem 0xfef00000-0xfeffffff] has been reserved
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267807] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267840] pnp 00:01: [dma 4]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267903] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.267995] pnp 00:02: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.268178] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.268256] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.288152] pnp 00:05: Plug and Play ACPI device, IDs PNP0303 (active)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.288243] pnp 00:06: Plug and Play ACPI device, IDs TOS0100 SYN0700 SYN0002 PNP0f13 (active)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.288702] pnp: PnP ACPI: found 7 devices
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.288708] ACPI: bus type PNP unregistered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.288715] PnPBIOS: Disabled by ACPI PNP
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329236] pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 05] add_size 1000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329250] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 05] add_size 200000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329258] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 05] add_size 200000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329275] pci 0000:00:1c.1: bridge window [io  0x1000-0x0fff] to [bus 07] add_size 1000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329283] pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 07] add_size 200000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329300] pci 0000:00:1c.2: bridge window [mem 0x00100000-0x000fffff] to [bus 09] add_size 400000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329329] pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329336] pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329344] pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329351] pci 0000:00:1c.2: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 400000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329359] pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329366] pci 0000:00:1c.1: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329380] pci 0000:00:1c.0: BAR 14: assigned [mem 0x80000000-0x801fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329391] pci 0000:00:1c.0: BAR 15: assigned [mem 0x80200000-0x803fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329402] pci 0000:00:1c.1: BAR 15: assigned [mem 0x80400000-0x805fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329411] pci 0000:00:1c.2: BAR 14: assigned [mem 0x80600000-0x809fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329422] pci 0000:00:1c.0: BAR 13: assigned [io  0x3000-0x3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329432] pci 0000:00:1c.1: BAR 13: assigned [io  0x4000-0x4fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329441] pci 0000:00:1d.7: BAR 0: assigned [mem 0x80a00000-0x80a003ff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329456] pci 0000:00:1f.2: BAR 5: assigned [mem 0x80a00400-0x80a007ff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329467] pci 0000:00:1c.0: PCI bridge to [bus 05]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329475] pci 0000:00:1c.0:   bridge window [io  0x3000-0x3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329485] pci 0000:00:1c.0:   bridge window [mem 0x80000000-0x801fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329495] pci 0000:00:1c.0:   bridge window [mem 0x80200000-0x803fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329506] pci 0000:00:1c.1: PCI bridge to [bus 07]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329513] pci 0000:00:1c.1:   bridge window [io  0x4000-0x4fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329523] pci 0000:00:1c.1:   bridge window [mem 0xf0100000-0xf01fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329532] pci 0000:00:1c.1:   bridge window [mem 0x80400000-0x805fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329543] pci 0000:00:1c.2: PCI bridge to [bus 09]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329551] pci 0000:00:1c.2:   bridge window [io  0x2000-0x2fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329561] pci 0000:00:1c.2:   bridge window [mem 0x80600000-0x809fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329570] pci 0000:00:1c.2:   bridge window [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329581] pci 0000:00:1e.0: PCI bridge to [bus 11]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329604] pci 0000:00:1c.0: enabling device (0000 -> 0003)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329944] pci 0000:00:1e.0: setting latency timer to 64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329955] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329962] pci_bus 0000:00: resource 5 [mem 0x000a0000-0x000bffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329969] pci_bus 0000:00: resource 6 [mem 0x000d0000-0x000d3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329975] pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329982] pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329988] pci_bus 0000:00: resource 9 [mem 0x000e0000-0x000e3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.329995] pci_bus 0000:00: resource 10 [mem 0x80000000-0xf7ffffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330002] pci_bus 0000:00: resource 11 [io  0x0d00-0xfdff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330008] pci_bus 0000:05: resource 0 [io  0x3000-0x3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330015] pci_bus 0000:05: resource 1 [mem 0x80000000-0x801fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330022] pci_bus 0000:05: resource 2 [mem 0x80200000-0x803fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330028] pci_bus 0000:07: resource 0 [io  0x4000-0x4fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330035] pci_bus 0000:07: resource 1 [mem 0xf0100000-0xf01fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330042] pci_bus 0000:07: resource 2 [mem 0x80400000-0x805fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330048] pci_bus 0000:09: resource 0 [io  0x2000-0x2fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330055] pci_bus 0000:09: resource 1 [mem 0x80600000-0x809fffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330061] pci_bus 0000:09: resource 2 [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330069] pci_bus 0000:11: resource 4 [io  0x0000-0x0cf7]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330075] pci_bus 0000:11: resource 5 [mem 0x000a0000-0x000bffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330082] pci_bus 0000:11: resource 6 [mem 0x000d0000-0x000d3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330088] pci_bus 0000:11: resource 7 [mem 0x000d4000-0x000d7fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330094] pci_bus 0000:11: resource 8 [mem 0x000d8000-0x000dbfff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330101] pci_bus 0000:11: resource 9 [mem 0x000e0000-0x000e3fff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330107] pci_bus 0000:11: resource 10 [mem 0x80000000-0xf7ffffff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330114] pci_bus 0000:11: resource 11 [io  0x0d00-0xfdff]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330186] NET: Registered protocol family 2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330518] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330583] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330640] TCP: Hash tables configured (established 8192 bind 8192)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330683] TCP: reno registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330690] UDP hash table entries: 512 (order: 2, 16384 bytes)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330708] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330844] NET: Registered protocol family 1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.330879] pci 0000:00:02.0: Boot video device
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.331892] PCI: CLS 32 bytes, default 64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    0.332070] Trying to unpack rootfs image as initramfs...
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.059890] Freeing initrd memory: 16544K (f5fa0000 - f6fc8000)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.060083] Simple Boot Flag at 0x35 set to 0x1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.060325] Scanning for low memory corruption every 60 seconds
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.060873] Initialise module verification
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.060983] audit: initializing netlink socket (disabled)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.061007] type=2000 audit(1385745443.060:1): initialized
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.113933] bounce pool size: 64 pages
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.113960] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.117410] zbud: loaded
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.117559] VFS: Disk quotas dquot_6.5.2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.117686] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.119010] fuse init (API version 7.22)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.119241] msgmni has been set to 1718
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.120385] Key type asymmetric registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.120394] Asymmetric key parser 'x509' registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.120506] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.120596] io scheduler noop registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.120604] io scheduler deadline registered (default)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.120682] io scheduler cfq registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.120931] pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.121075] pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.121202] pcieport 0000:00:1c.2: irq 42 for MSI/MSI-X
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.121357] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.121402] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.121561] intel_idle: MWAIT substates: 0x20220
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.121579] intel_idle: v0.4 model 0x1C
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.121584] intel_idle: lapic_timer_reliable_states 0x2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.122250] ACPI: AC Adapter [ACAD] (on-line)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.122691] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0d/PNP0C0D:00/input/input0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.122868] ACPI: Lid Switch [LID0]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.122985] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0A08:00/PNP0C0C:00/input/input1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.122996] ACPI: Power Button [PWRB]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.123097] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.123105] ACPI: Power Button [PWRF]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.123245] ACPI: Requesting acpi_cpufreq
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.127940] GHES: HEST is not enabled!
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.128207] isapnp: Scanning for PnP cards...
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.132202] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.136461] Linux agpgart interface v0.103
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.136629] agpgart-intel 0000:00:00.0: Intel GMA3150 Chipset
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.136772] agpgart-intel 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.136957] agpgart-intel 0000:00:00.0: detected 8192K stolen memory
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.137187] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.141811] brd: module loaded
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.144199] loop: module loaded
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.145487] libphy: Fixed MDIO Bus: probed
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.145810] tun: Universal TUN/TAP device driver, 1.6
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.145816] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.145942] PPP generic driver version 2.4.2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.146063] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.146069] ehci-pci: EHCI PCI platform driver
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.146281] ehci-pci 0000:00:1d.7: setting latency timer to 64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.146304] ehci-pci 0000:00:1d.7: EHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.146323] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.146350] ehci-pci 0000:00:1d.7: debug port 1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.150286] ehci-pci 0000:00:1d.7: cache line size of 32 is not supported
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.151963] ehci-pci 0000:00:1d.7: irq 23, io mem 0x80a00000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.160036] ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.160098] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.160108] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.160115] usb usb1: Product: EHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.160123] usb usb1: Manufacturer: Linux 3.11.0-13-generic ehci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.160130] usb usb1: SerialNumber: 0000:00:1d.7
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.160466] hub 1-0:1.0: USB hub found
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.160481] hub 1-0:1.0: 8 ports detected
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161373] ehci-platform: EHCI generic platform driver
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161406] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161411] ohci-platform: OHCI generic platform driver
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161445] uhci_hcd: USB Universal Host Controller Interface driver
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161631] uhci_hcd 0000:00:1d.0: setting latency timer to 64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161642] uhci_hcd 0000:00:1d.0: UHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161659] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161704] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001820
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161791] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161800] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161807] usb usb2: Product: UHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161815] usb usb2: Manufacturer: Linux 3.11.0-13-generic uhci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.161822] usb usb2: SerialNumber: 0000:00:1d.0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162126] hub 2-0:1.0: USB hub found
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162140] hub 2-0:1.0: 2 ports detected
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162501] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162511] uhci_hcd 0000:00:1d.1: UHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162528] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162595] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001840
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162682] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162691] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162699] usb usb3: Product: UHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162706] usb usb3: Manufacturer: Linux 3.11.0-13-generic uhci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.162714] usb usb3: SerialNumber: 0000:00:1d.1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163014] hub 3-0:1.0: USB hub found
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163028] hub 3-0:1.0: 2 ports detected
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163476] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163487] uhci_hcd 0000:00:1d.2: UHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163503] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163572] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001860
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163656] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163665] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163673] usb usb4: Product: UHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163681] usb usb4: Manufacturer: Linux 3.11.0-13-generic uhci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163688] usb usb4: SerialNumber: 0000:00:1d.2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.163986] hub 4-0:1.0: USB hub found
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164001] hub 4-0:1.0: 2 ports detected
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164457] uhci_hcd 0000:00:1d.3: setting latency timer to 64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164468] uhci_hcd 0000:00:1d.3: UHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164489] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164553] uhci_hcd 0000:00:1d.3: irq 16, io base 0x00001880
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164643] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164652] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164660] usb usb5: Product: UHCI Host Controller
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164668] usb usb5: Manufacturer: Linux 3.11.0-13-generic uhci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164675] usb usb5: SerialNumber: 0000:00:1d.3
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.164988] hub 5-0:1.0: USB hub found
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.165003] hub 5-0:1.0: 2 ports detected
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.165516] i8042: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.184224] serio: i8042 KBD port at 0x60,0x64 irq 1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.184260] serio: i8042 AUX port at 0x60,0x64 irq 12
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.184846] mousedev: PS/2 mouse device common for all mice
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.186195] rtc_cmos 00:03: RTC can wake from S4
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.186414] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.186462] rtc_cmos 00:03: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.186658] device-mapper: uevent: version 1.0.3
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.186848] device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised: dm-devel@redhat.com
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.186914] platform eisa.0: Probing EISA bus 0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.186949] platform eisa.0: EISA: Detected 0 cards
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.186968] cpufreq-nforce2: No nForce2 chipset.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.187098] cpuidle: using governor ladder
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.187264] cpuidle: using governor menu
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.187302] ledtrig-cpu: registered to indicate activity on CPUs
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.187543] TCP: cubic registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.187858] NET: Registered protocol family 10
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.188401] NET: Registered protocol family 17
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.188431] Key type dns_resolver registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.188905] Using IPI No-Shortcut mode
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.189151] PM: Hibernation image not present or could not be loaded.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.189162] Loading module verification certificates
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.202884] MODSIGN: Loaded cert 'Magrathea: Glacier signing key: 121c3931998f688796d5ac98c50cd636878ded2d'
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.202919] registered taskstats version 1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.210522] Key type trusted registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.217407] Key type encrypted registered
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.218017] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.225455] AppArmor: AppArmor sha1 policy hashing enabled
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.226128]   Magic number: 5:733:290
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.226195] tty tty23: hash matches
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.226285] rtc_cmos 00:03: setting system clock to 2013-11-29 17:17:23 UTC (1385745443)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.227259] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.227267] EDD information not available.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.324477] [Firmware Bug]: battery: (dis)charge rate invalid.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.324557] ACPI: Battery Slot [BAT1] (battery present)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.482029] isapnp: No Plug & Play device found
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.482665] Freeing unused kernel memory: 880K (c1962000 - c1a3e000)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.482777] Write protecting the kernel text: 6356k
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.482919] Write protecting the kernel read-only data: 2644k
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.482924] NX-protecting the kernel data: 5932k
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.609692] mii: module verification failed: signature and/or required key missing - tainting kernel
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.627211] ahci 0000:00:1f.2: version 3.0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.627468] ahci 0000:00:1f.2: irq 43 for MSI/MSI-X
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.627595] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.627608] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part 
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.627621] ahci 0000:00:1f.2: setting latency timer to 64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.635693] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.635730] r8169 0000:09:00.0: can't disable ASPM; OS doesn't have ASPM control
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.636100] scsi0 : ahci
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.636143] r8169 0000:09:00.0: irq 44 for MSI/MSI-X
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.636692] r8169 0000:09:00.0 eth0: RTL8168e/8111e at 0xf8422000, 88:ae:1d:f4:54:83, XID 0c200000 IRQ 44
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.636705] r8169 0000:09:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.637148] scsi1 : ahci
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.637468] scsi2 : ahci
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.637756] scsi3 : ahci
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.638030] ata1: SATA max UDMA/133 abar m1024@0x80a00400 port 0x80a00500 irq 43
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.638041] ata2: SATA max UDMA/133 abar m1024@0x80a00400 port 0x80a00580 irq 43
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.638050] ata3: SATA max UDMA/133 abar m1024@0x80a00400 port 0x80a00600 irq 43
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.638059] ata4: SATA max UDMA/133 abar m1024@0x80a00400 port 0x80a00680 irq 43
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.744097] usb 1-4: new high-speed USB device number 3 using ehci-pci
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.956131] ata4: SATA link down (SStatus 0 SControl 300)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.956172] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.956204] ata3: SATA link down (SStatus 0 SControl 300)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.956234] ata2: SATA link down (SStatus 0 SControl 300)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.957296] ata1.00: ATA-8: Hitachi HTS545025B9A300, PB2OC64G, max UDMA/133
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.957309] ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.958568] ata1.00: configured for UDMA/133
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.958929] scsi 0:0:0:0: Direct-Access     ATA      Hitachi HTS54502 PB2O PQ: 0 ANSI: 5
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.959598] sd 0:0:0:0: Attached scsi generic sg0 type 0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.959741] sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.959991] sd 0:0:0:0: [sda] Write Protect is off
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.960004] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    1.960170] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.007830]  sda: sda1 sda2 sda3 < sda5 sda6 >
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.009231] sd 0:0:0:0: [sda] Attached SCSI disk
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.132822] usb 1-4: New USB device found, idVendor=0bda, idProduct=0138
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.132832] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.132839] usb 1-4: Product: USB2.0-CRW
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.132844] usb 1-4: Manufacturer: Generic
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.132850] usb 1-4: SerialNumber: 20090516388200000
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.400303] usbcore: registered new interface driver usb-storage
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.413776] ums-realtek 1-4:1.0: USB Mass Storage device detected
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.432910] scsi4 : usb-storage 1-4:1.0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.433161] usbcore: registered new interface driver ums-realtek
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.636051] usb 2-2: new full-speed USB device number 2 using uhci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.787888] usb 2-2: New USB device found, idVendor=0a12, idProduct=0001
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.787900] usb 2-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    2.843653] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    3.028110] usb 5-2: new full-speed USB device number 2 using uhci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    3.148110] usb 5-2: device descriptor read/64, error -71
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    3.372132] usb 5-2: device descriptor read/64, error -71
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    3.644086] usb 5-2: new full-speed USB device number 3 using uhci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    3.764095] usb 5-2: device descriptor read/64, error -71
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    3.988132] usb 5-2: device descriptor read/64, error -71
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    4.204072] usb 5-2: new full-speed USB device number 4 using uhci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    4.612101] usb 5-2: device not accepting address 4, error -71
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    4.724111] usb 5-2: new full-speed USB device number 5 using uhci_hcd
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    5.136073] usb 5-2: device not accepting address 5, error -71
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    5.136126] hub 5-0:1.0: unable to enumerate USB device on port 2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    5.264127] usb 1-4: USB disconnect, device number 3
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    5.341074] Adding 2084860k swap on /dev/sda5.  Priority:-1 extents:1 across:2084860k FS
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    6.659392] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    8.316220] lp: driver loaded but no devices found
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    8.871203] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.569725] wmi: Mapper loaded
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.673013] ACPI Warning: 0x00001028-0x0000102f SystemIO conflicts with Region \_SB_.PCI0.LPC0.PMIO 1 (20130517/utaddress-251)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.673033] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.673042] ACPI Warning: 0x000011b0-0x000011bf SystemIO conflicts with Region \_SB_.PCI0.LPC0.GPIO 1 (20130517/utaddress-251)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.673056] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.673063] ACPI Warning: 0x00001180-0x000011af SystemIO conflicts with Region \_SB_.PCI0.LPC0.GPIO 1 (20130517/utaddress-251)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.673076] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.673081] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.804782] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.805027] input: Toshiba input device as /devices/virtual/input/input4
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [    9.955870] [drm] Initialized drm 1.1.0 20060810
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.043608] Bluetooth: Core ver 2.16
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.052500] NET: Registered protocol family 31
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.052510] Bluetooth: HCI device and connection manager initialized
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.052527] Bluetooth: HCI socket layer initialized
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.052537] Bluetooth: L2CAP socket layer initialized
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.052558] Bluetooth: SCO socket layer initialized
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.074796] microcode: CPU0 sig=0x106ca, pf=0x4, revision=0x107
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.096832] cfg80211: Calling CRDA to update world regulatory domain
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.184000] usbcore: registered new interface driver btusb
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.526998] [drm] Memory usable by graphics device = 512M
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.527022] i915 0000:00:02.0: setting latency timer to 64
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.528431] i915 0000:00:02.0: irq 45 for MSI/MSI-X
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.528473] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.528480] [drm] Driver supports precise vblank timestamp query.
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.528623] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.626463] [drm] initialized overlay support
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   10.947894] fbcon: inteldrmfb (fb0) is primary device
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.295938] ath: phy0: ASPM enabled: 0x43
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.295942] ath: EEPROM regdomain: 0x65
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.295944] ath: EEPROM indicates we should expect a direct regpair map
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.295948] ath: Country alpha2 being used: 00
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.295949] ath: Regpair used: 0x65
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.364175] Console: switching to colour frame buffer device 128x37
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.373018] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.373025] i915 0000:00:02.0: registered panic notifier
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.375163] acpi device:01: registered as cooling_device2
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.375271] ACPI: Video Device [IGD0] (multi-head: yes  rom: no  post: no)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.375550] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.376001] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.376391] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.395909] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04733/0xa40000/0xa0000, board id: 3655, fw id: 528321
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.407188] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.408367] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf86e0000, irq=17
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.471475] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.588828] SKU: Nid=0x1d sku_cfg=0x4017992d
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.588835] SKU: port_connectivity=0x1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.588839] SKU: enable_pcbeep=0x1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.588843] SKU: check_sum=0x00000007
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.588846] SKU: customization=0x00000099
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.588850] SKU: external_amp=0x5
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.588853] SKU: platform_type=0x1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.588857] SKU: swap=0x0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.588860] SKU: override=0x1
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.589384] autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.589390]    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.589395]    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.589399]    mono: mono_out=0x0
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.589402]    inputs:
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.589407]      Internal Mic=0x19
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.589411]      Mic=0x18
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.589416] realtek: No valid SSID, checking pincfg 0x4017992d for NID 0x1d
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.589421] realtek: Enabling init ASM_ID=0x992d CODEC_ID=10ec0269
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.595406] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.595702] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.766719] type=1400 audit(1385741854.033:2): apparmor="STATUS" operation="profile_load" parent=340 profile="unconfined" name="/sbin/dhclient" pid=342 comm="apparmor_parser"
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.766741] type=1400 audit(1385741854.033:3): apparmor="STATUS" operation="profile_load" parent=340 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=342 comm="apparmor_parser"
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.766756] type=1400 audit(1385741854.033:4): apparmor="STATUS" operation="profile_load" parent=340 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=342 comm="apparmor_parser"
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.768618] type=1400 audit(1385741854.037:5): apparmor="STATUS" operation="profile_replace" parent=340 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=342 comm="apparmor_parser"
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.768639] type=1400 audit(1385741854.037:6): apparmor="STATUS" operation="profile_replace" parent=340 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=342 comm="apparmor_parser"
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.769592] type=1400 audit(1385741854.037:7): apparmor="STATUS" operation="profile_replace" parent=340 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=342 comm="apparmor_parser"
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   11.952006] type=1400 audit(1385741854.221:8): apparmor="STATUS" operation="profile_load" parent=340 profile="unconfined" name="/usr/sbin/ntpd" pid=417 comm="apparmor_parser"
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   12.499506] microcode: CPU1 sig=0x106ca, pf=0x4, revision=0x107
Nov 29 17:17:34 nava-TOSHIBA-NB250 kernel: [   12.631670] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov 29 17:17:36 nava-TOSHIBA-NB250 kernel: [   13.933927] cfg80211: World regulatory domain updated:
Nov 29 17:17:36 nava-TOSHIBA-NB250 kernel: [   13.933936] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 29 17:17:36 nava-TOSHIBA-NB250 kernel: [   13.933943] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 17:17:36 nava-TOSHIBA-NB250 kernel: [   13.933948] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 17:17:36 nava-TOSHIBA-NB250 kernel: [   13.933954] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 29 17:17:36 nava-TOSHIBA-NB250 kernel: [   13.933959] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 17:17:36 nava-TOSHIBA-NB250 kernel: [   13.933964] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 29 17:17:38 nava-TOSHIBA-NB250 kernel: [   15.970265] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Nov 29 17:17:38 nava-TOSHIBA-NB250 kernel: [   15.970275] Bluetooth: BNEP filters: protocol multicast
Nov 29 17:17:38 nava-TOSHIBA-NB250 kernel: [   15.970294] Bluetooth: BNEP socket layer initialized
Nov 29 17:17:38 nava-TOSHIBA-NB250 kernel: [   15.987599] Bluetooth: RFCOMM TTY layer initialized
Nov 29 17:17:38 nava-TOSHIBA-NB250 kernel: [   15.987631] Bluetooth: RFCOMM socket layer initialized
Nov 29 17:17:38 nava-TOSHIBA-NB250 kernel: [   15.987638] Bluetooth: RFCOMM ver 1.11
Nov 29 17:17:38 nava-TOSHIBA-NB250 kernel: [   16.091225] ppdev: user-space parallel port driver
Nov 29 17:17:38 nava-TOSHIBA-NB250 modem-manager[584]: <info>  ModemManager (version 0.6.0.0) starting...
Nov 29 17:17:39 nava-TOSHIBA-NB250 kernel: [   16.881982] type=1400 audit(1385741859.149:9): apparmor="STATUS" operation="profile_load" parent=619 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=623 comm="apparmor_parser"
Nov 29 17:17:39 nava-TOSHIBA-NB250 kernel: [   16.882006] type=1400 audit(1385741859.149:10): apparmor="STATUS" operation="profile_load" parent=619 profile="unconfined" name="/usr/sbin/cupsd" pid=623 comm="apparmor_parser"
Nov 29 17:17:39 nava-TOSHIBA-NB250 kernel: [   16.884213] type=1400 audit(1385741859.153:11): apparmor="STATUS" operation="profile_replace" parent=619 profile="unconfined" name="/usr/sbin/cupsd" pid=623 comm="apparmor_parser"
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'X22X'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Sierra'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Option'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Huawei'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Ericsson MBM'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Nokia'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Wavecom'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Longcheer'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Linktop'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'MotoC'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Novatel'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Option High-Speed'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'SimTech'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'ZTE'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'AnyData'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Samsung'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Gobi'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Cinterion'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Iridium'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Loaded plugin 'Generic'
Nov 29 17:17:40 nava-TOSHIBA-NB250 modem-manager[584]: <info>  Successfully loaded 20 plugins
Nov 29 17:17:40 nava-TOSHIBA-NB250 NetworkManager[628]: <info> NetworkManager (version 0.9.8.0) is starting...
Nov 29 17:17:40 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Nov 29 17:17:40 nava-TOSHIBA-NB250 NetworkManager[628]: <info> WEXT support is enabled
Nov 29 17:17:41 nava-TOSHIBA-NB250 NetworkManager[628]: <info> DNS: loaded plugin dnsmasq
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: init!
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: update_system_hostname
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPluginIfupdown: management mode: unmanaged
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:07:00.0/net/wlan0, iface: wlan0)
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:07:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0/net/eth0, iface: eth0)
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0/net/eth0, iface: eth0): no ifupdown configuration found.
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: end _init.
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ofono: Acquired D-Bus service com.canonical.NMOfono
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ofono: init!
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ofono: end _init.
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Loaded plugin (null): (null)
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    Ifupdown: get unmanaged devices count: 0
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: (152059032) ... get_connections.
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ifupdown: (152059032) ... get_connections (managed=false): return empty list.
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    keyfile: parsing Priya 2 ... 
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    keyfile:     read connection 'Priya 2'
Nov 29 17:17:42 nava-TOSHIBA-NB250 NetworkManager[628]:    keyfile: parsing FRITZ!Box WLAN 3370 ... 
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]:    keyfile:     read connection 'FRITZ!Box WLAN 3370'
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]:    keyfile: parsing Priya ... 
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]:    keyfile:     read connection 'Priya'
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]:    keyfile: parsing Priya 1 ... 
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]:    keyfile:     read connection 'Priya 1'
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ofono: (151974352) ... get_connections.
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]:    SCPlugin-Ofono: (151974352) connections count: 0
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]:    Ifupdown: get unmanaged devices count: 0
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> modem-manager is now available
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> monitoring kernel firmware directory '/lib/firmware'.
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:07:00.0/ieee80211/phy0/rfkill1) (driver ath9k)
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> WiFi hardware radio set enabled
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> WiFi enabled by radio killswitch; enabled by state file
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Networking is enabled by state file
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): using nl80211 for WiFi device control
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): driver supports Access Point (AP) mode
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): bringing up device.
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): preparing device.
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): deactivating device (reason 'managed') [2]
Nov 29 17:17:43 nava-TOSHIBA-NB250 kernel: [   21.398870] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 29 17:17:43 nava-TOSHIBA-NB250 kernel: [   21.399859] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> failed to allocate link cache: (-10) Operation not supported
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (eth0): carrier is OFF
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (eth0): bringing up device.
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (eth0): preparing device.
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (eth0): deactivating device (reason 'managed') [2]
Nov 29 17:17:43 nava-TOSHIBA-NB250 kernel: [   21.649227] r8169 0000:09:00.0 eth0: link down
Nov 29 17:17:43 nava-TOSHIBA-NB250 kernel: [   21.649309] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 29 17:17:43 nava-TOSHIBA-NB250 kernel: [   21.650516] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Added default wired connection '1. vezetékes kapcsolat' for /sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0/net/eth0
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Nov 29 17:17:43 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Nov 29 17:17:44 nava-TOSHIBA-NB250 NetworkManager[628]: <info> wpa_supplicant started
Nov 29 17:17:44 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0) supports 4 scan SSIDs
Nov 29 17:17:44 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> Trying to remove a non-existant call id.
Nov 29 17:17:44 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): supplicant interface state: starting -> ready
Nov 29 17:17:44 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Nov 29 17:17:44 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): supplicant interface state: ready -> inactive
Nov 29 17:17:44 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0) supports 4 scan SSIDs
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.385829] type=1400 audit(1385741864.653:12): apparmor="STATUS" operation="profile_replace" parent=696 profile="unconfined" name="/sbin/dhclient" pid=704 comm="apparmor_parser"
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.385863] type=1400 audit(1385741864.653:13): apparmor="STATUS" operation="profile_replace" parent=696 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=704 comm="apparmor_parser"
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.385887] type=1400 audit(1385741864.653:14): apparmor="STATUS" operation="profile_replace" parent=696 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=704 comm="apparmor_parser"
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.391019] type=1400 audit(1385741864.657:15): apparmor="STATUS" operation="profile_replace" parent=696 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=704 comm="apparmor_parser"
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.391051] type=1400 audit(1385741864.657:16): apparmor="STATUS" operation="profile_replace" parent=696 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=704 comm="apparmor_parser"
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.400719] type=1400 audit(1385741864.669:17): apparmor="STATUS" operation="profile_replace" parent=696 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=704 comm="apparmor_parser"
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.451280] type=1400 audit(1385741864.717:18): apparmor="STATUS" operation="profile_load" parent=696 profile="unconfined" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=703 comm="apparmor_parser"
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.451310] type=1400 audit(1385741864.717:19): apparmor="STATUS" operation="profile_load" parent=696 profile="unconfined" name="chromium_browser" pid=703 comm="apparmor_parser"
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.457663] type=1400 audit(1385741864.725:20): apparmor="STATUS" operation="profile_replace" parent=696 profile="unconfined" name="chromium_browser" pid=703 comm="apparmor_parser"
Nov 29 17:17:44 nava-TOSHIBA-NB250 kernel: [   22.587020] type=1400 audit(1385741864.853:21): apparmor="STATUS" operation="profile_replace" parent=696 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=713 comm="apparmor_parser"
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Auto-activating connection 'Priya 1'.
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) starting connection 'Priya 1'
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0/wireless): connection 'Priya 1' has security, and secrets exist.  No new secrets needed.
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Config: added 'ssid' value 'Priya'
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Config: added 'scan_ssid' value '1'
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Config: added 'auth_alg' value 'OPEN'
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Config: added 'psk' value '<omitted>'
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Config: set interface ap_scan to 1
Nov 29 17:17:45 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): supplicant interface state: inactive -> scanning
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.053516] zram: module is from the staging directory, the quality is unknown, you have been warned.
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.061719] zram: Created 2 device(s) ...
Nov 29 17:17:46 nava-TOSHIBA-NB250 wpa_supplicant[694]: wlan0: SME: Trying to authenticate with 94:0c:6d:fe:84:60 (SSID='Priya' freq=2412 MHz)
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.100619] wlan0: authenticate with 94:0c:6d:fe:84:60
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.147414] wlan0: send auth to 94:0c:6d:fe:84:60 (try 1/3)
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.150483] wlan0: authenticated
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.157354] ath9k 0000:07:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.157368] ath9k 0000:07:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.160434] wlan0: associate with 94:0c:6d:fe:84:60 (try 1/3)
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.163036] wlan0: RX AssocResp from 94:0c:6d:fe:84:60 (capab=0x431 status=0 aid=2)
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.163846] wlan0: associated
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.163911] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov 29 17:17:46 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 29 17:17:46 nava-TOSHIBA-NB250 wpa_supplicant[694]: wlan0: Trying to associate with 94:0c:6d:fe:84:60 (SSID='Priya' freq=2412 MHz)
Nov 29 17:17:46 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): supplicant interface state: authenticating -> associating
Nov 29 17:17:46 nava-TOSHIBA-NB250 wpa_supplicant[694]: wlan0: Associated with 94:0c:6d:fe:84:60
Nov 29 17:17:46 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): supplicant interface state: associating -> associated
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.307780] Adding 513572k swap on /dev/zram0.  Priority:5 extents:1 across:513572k SSFS
Nov 29 17:17:46 nava-TOSHIBA-NB250 kernel: [   24.334019] Adding 513572k swap on /dev/zram1.  Priority:5 extents:1 across:513572k SSFS
Nov 29 17:17:47 nava-TOSHIBA-NB250 wpa_supplicant[694]: wlan0: WPA: Key negotiation completed with 94:0c:6d:fe:84:60 [PTK=CCMP GTK=TKIP]
Nov 29 17:17:47 nava-TOSHIBA-NB250 wpa_supplicant[694]: wlan0: CTRL-EVENT-CONNECTED - Connection to 94:0c:6d:fe:84:60 completed (auth) [id=0 id_str=]
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Priya'.
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> dhclient started with pid 969
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Beginning IP6 addrconf.
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Nov 29 17:17:47 nava-TOSHIBA-NB250 dhclient: Internet Systems Consortium DHCP Client 4.2.4
Nov 29 17:17:47 nava-TOSHIBA-NB250 dhclient: Copyright 2004-2012 Internet Systems Consortium.
Nov 29 17:17:47 nava-TOSHIBA-NB250 dhclient: All rights reserved.
Nov 29 17:17:47 nava-TOSHIBA-NB250 dhclient: For info, please visit https://www.isc.org/software/dhcp/
Nov 29 17:17:47 nava-TOSHIBA-NB250 dhclient: 
Nov 29 17:17:47 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Nov 29 17:17:47 nava-TOSHIBA-NB250 dhclient: Listening on LPF/wlan0/00:26:4d:f3:50:69
Nov 29 17:17:47 nava-TOSHIBA-NB250 dhclient: Sending on   LPF/wlan0/00:26:4d:f3:50:69
Nov 29 17:17:47 nava-TOSHIBA-NB250 dhclient: Sending on   Socket/fallback
Nov 29 17:17:47 nava-TOSHIBA-NB250 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x30fe2e04)
Nov 29 17:17:50 nava-TOSHIBA-NB250 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 (xid=0x30fe2e04)
Nov 29 17:17:51 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 255.255.255.255 port 67 (xid=0x30fe2e04)
Nov 29 17:17:51 nava-TOSHIBA-NB250 dhclient: DHCPOFFER of 192.168.1.101 from 192.168.1.1
Nov 29 17:17:51 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 29 17:17:51 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 2767 seconds.
Nov 29 17:17:51 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Nov 29 17:17:51 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   address 192.168.1.101
Nov 29 17:17:51 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   prefix 24 (255.255.255.0)
Nov 29 17:17:51 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   gateway 192.168.1.1
Nov 29 17:17:51 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.2.1'
Nov 29 17:17:51 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.1.1'
Nov 29 17:17:51 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Nov 29 17:17:51 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Nov 29 17:17:52 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Nov 29 17:17:52 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Nov 29 17:17:52 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 29 17:17:52 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Policy set 'Priya 1' (wlan0) as default for IPv4 routing and DNS.
Nov 29 17:17:52 nava-TOSHIBA-NB250 NetworkManager[628]: <info> DNS: starting dnsmasq...
Nov 29 17:17:52 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> dnsmasq not available on the bus, can't update servers.
Nov 29 17:17:52 nava-TOSHIBA-NB250 NetworkManager[628]: <error> [1385741872.307328] [nm-dns-dnsmasq.c:402] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Nov 29 17:17:52 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> DNS: plugin dnsmasq update failed
Nov 29 17:17:52 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Writing DNS information to /sbin/resolvconf
Nov 29 17:17:54 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) successful, device activated.
Nov 29 17:17:54 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> dnsmasq appeared on DBus: :1.21
Nov 29 17:17:54 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Writing DNS information to /sbin/resolvconf
Nov 29 17:18:07 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): IP6 addrconf timed out or failed.
Nov 29 17:18:07 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Nov 29 17:18:07 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Nov 29 17:18:07 nava-TOSHIBA-NB250 NetworkManager[628]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Nov 29 17:33:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 17:35:24 nava-TOSHIBA-NB250 kernel: [ 1082.206974] perf samples too long (2617 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Nov 29 17:41:41 nava-TOSHIBA-NB250 kernel: [ 1458.649550] perf samples too long (5042 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
Nov 29 17:52:13 nava-TOSHIBA-NB250 kernel: [ 2090.404859] perf samples too long (10089 > 10000), lowering kernel.perf_event_max_sample_rate to 12500
Nov 29 17:55:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 18:03:58 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 192.168.1.1 port 67 (xid=0x30fe2e04)
Nov 29 18:03:58 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 29 18:03:58 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 3111 seconds.
Nov 29 18:03:58 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): DHCPv4 state changed bound -> renew
Nov 29 18:03:58 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   address 192.168.1.101
Nov 29 18:03:58 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   prefix 24 (255.255.255.0)
Nov 29 18:03:58 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   gateway 192.168.1.1
Nov 29 18:03:58 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.2.1'
Nov 29 18:03:58 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.1.1'
Nov 29 18:07:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 18:20:59 nava-TOSHIBA-NB250 kernel: [ 3816.528231] usb 1-1: new high-speed USB device number 5 using ehci-pci
Nov 29 18:20:59 nava-TOSHIBA-NB250 kernel: [ 3816.664795] usb 1-1: New USB device found, idVendor=05ac, idProduct=1293
Nov 29 18:20:59 nava-TOSHIBA-NB250 kernel: [ 3816.664825] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 29 18:20:59 nava-TOSHIBA-NB250 kernel: [ 3816.664834] usb 1-1: Product: iPod
Nov 29 18:20:59 nava-TOSHIBA-NB250 kernel: [ 3816.664860] usb 1-1: Manufacturer: Apple Inc.
Nov 29 18:20:59 nava-TOSHIBA-NB250 kernel: [ 3816.664868] usb 1-1: SerialNumber: 8b556da75e399a646eba36a7f9cb10cf6e463dc7
Nov 29 18:37:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 18:41:03 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 18:45:04 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 18:55:49 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 192.168.1.1 port 67 (xid=0x30fe2e04)
Nov 29 18:55:49 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 29 18:55:49 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 3507 seconds.
Nov 29 18:55:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): DHCPv4 state changed renew -> renew
Nov 29 18:55:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   address 192.168.1.101
Nov 29 18:55:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   prefix 24 (255.255.255.0)
Nov 29 18:55:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   gateway 192.168.1.1
Nov 29 18:55:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.2.1'
Nov 29 18:55:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.1.1'
Nov 29 19:01:03 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 19:45:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 19:54:16 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 192.168.1.1 port 67 (xid=0x30fe2e04)
Nov 29 19:54:16 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 29 19:54:16 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 2853 seconds.
Nov 29 19:54:16 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): DHCPv4 state changed renew -> renew
Nov 29 19:54:16 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   address 192.168.1.101
Nov 29 19:54:16 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   prefix 24 (255.255.255.0)
Nov 29 19:54:16 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   gateway 192.168.1.1
Nov 29 19:54:16 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.2.1'
Nov 29 19:54:16 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.1.1'
Nov 29 20:05:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 20:33:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 20:35:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 20:39:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 20:41:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 20:41:49 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 192.168.1.1 port 67 (xid=0x30fe2e04)
Nov 29 20:41:49 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 29 20:41:49 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 3081 seconds.
Nov 29 20:41:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): DHCPv4 state changed renew -> renew
Nov 29 20:41:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   address 192.168.1.101
Nov 29 20:41:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   prefix 24 (255.255.255.0)
Nov 29 20:41:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   gateway 192.168.1.1
Nov 29 20:41:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.2.1'
Nov 29 20:41:49 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.1.1'
Nov 29 20:49:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 20:53:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 20:55:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 20:56:11 nava-TOSHIBA-NB250 kernel: [13129.386553] usb 1-1: USB disconnect, device number 5
Nov 29 21:01:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 21:17:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 21:19:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 21:21:02 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 21:33:10 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 192.168.1.1 port 67 (xid=0x30fe2e04)
Nov 29 21:33:10 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 29 21:33:10 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 3143 seconds.
Nov 29 21:33:10 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): DHCPv4 state changed renew -> renew
Nov 29 21:33:10 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   address 192.168.1.101
Nov 29 21:33:10 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   prefix 24 (255.255.255.0)
Nov 29 21:33:10 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   gateway 192.168.1.1
Nov 29 21:33:10 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.2.1'
Nov 29 21:33:10 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.1.1'
Nov 29 22:25:33 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 192.168.1.1 port 67 (xid=0x30fe2e04)
Nov 29 22:25:33 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 29 22:25:33 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 2959 seconds.
Nov 29 22:25:33 nava-TOSHIBA-NB250 NetworkManager[628]: <info> (wlan0): DHCPv4 state changed renew -> renew
Nov 29 22:25:33 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   address 192.168.1.101
Nov 29 22:25:33 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   prefix 24 (255.255.255.0)
Nov 29 22:25:33 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   gateway 192.168.1.1
Nov 29 22:25:33 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.2.1'
Nov 29 22:25:33 nava-TOSHIBA-NB250 NetworkManager[628]: <info>   nameserver '192.168.1.1'
Nov 29 22:38:12 nava-TOSHIBA-NB250 kernel: [19249.848200] hda-codec: out of range cmd 0:20:400:ffffffff
Nov 29 22:41:03 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 29 22:53:03 nava-TOSHIBA-NB250 NetworkManager[628]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Linux version 3.11.0-13-generic (buildd@aatxe) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) ) #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013 (Ubuntu 3.11.0-13.20-generic 3.11.6)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] KERNEL supported cpus:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   Intel GenuineIntel
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   AMD AuthenticAMD
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   NSC Geode by NSC
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   Cyrix CyrixInstead
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   Centaur CentaurHauls
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   Transmeta GenuineTMx86
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   Transmeta TransmetaCPU
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   UMC UMC UMC UMC
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009dbff] usable
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009dc00-0x000000000009ffff] reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000dc000-0x00000000000dffff] reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e4000-0x00000000000fffff] reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007f5cffff] usable
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x000000007f5d0000-0x000000007f5dffff] ACPI data
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x000000007f5e0000-0x000000007f5e2fff] ACPI NVS
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x000000007f5e3000-0x000000007fffffff] reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] SMBIOS 2.5 present.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] DMI: TOSHIBA TOSHIBA NB250/PAV10 DDR3, BIOS V1.60 07/30/2010
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: last_pfn = 0x7f5d0 max_arch_pfn = 0x1000000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] MTRR default type: uncachable
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   00000-9FFFF write-back
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   C0000-CFFFF write-protect
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   D0000-DFFFF uncachable
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   E0000-FFFFF write-protect
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] MTRR variable ranges enabled:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   0 base 000000000 mask 080000000 write-back
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   1 base 07F600000 mask 0FFE00000 uncachable
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   2 base 07F800000 mask 0FF800000 uncachable
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   3 disabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   4 disabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   5 disabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   6 disabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   7 disabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] original variable MTRRs
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 0, base: 0GB, range: 2GB, type WB
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 1, base: 2038MB, range: 2MB, type UC
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 2, base: 2040MB, range: 8MB, type UC
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] total RAM covered: 2038M
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Found optimal setting for mtrr clean up
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]  gran_size: 64K 	chunk_size: 16M 	num_reg: 3  	lose cover RAM: 0G
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] New variable MTRRs
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 0, base: 0GB, range: 2GB, type WB
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 1, base: 2038MB, range: 2MB, type UC
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] reg 2, base: 2040MB, range: 8MB, type UC
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] found SMP MP-table at [mem 0x000f7d30-0x000f7d3f] mapped at [c00f7d30]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] initial memory mapped: [mem 0x00000000-0x01ffffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Base memory trampoline at [c0099000] 99000 size 16384
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x37800000-0x379fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x37800000-0x379fffff] page 2M
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x34000000-0x377fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x34000000-0x377fffff] page 2M
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x33ffffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x00200000-0x33ffffff] page 2M
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] init_memory_mapping: [mem 0x37a00000-0x37bfdfff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]  [mem 0x37a00000-0x37bfdfff] page 4k
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BRK [0x01b39000, 0x01b39fff] PGTABLE
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] RAMDISK: [mem 0x35fa0000-0x36fc7fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: RSDP 000f7c90 00024 (v02 TOSCPL)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: XSDT 7f5d7ae1 00074 (v01 TOSCPL TOSCPL00 06040000  LTP 00000000)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: FACP 7f5dfc60 000F4 (v03 TOSCPL TOSCPL00 06040000 PTL  00000002)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: DSDT 7f5d8c77 06F75 (v01 TOSCPL TOSCPL00 06040000 MSFT 03000000)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: FACS 7f5e2fc0 00040
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: TCPA 7f5dfd54 00032 (v01 Phoeni  x       06040000  TL  00000000)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: HPET 7f5dfd86 00038 (v01 DELL   M09      06040000 LOHR 0000005A)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: MCFG 7f5dfdbe 0003C (v01 INTEL  CRESTLNE 06040000 LOHR 0000005A)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: SLIC 7f5dfdfa 00176 (v01 TOSCPL TOSCPL00 06040000 LOHR 00000000)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: APIC 7f5dff70 00068 (v01 TOSCPL TOSCPL00 06040000  LTP 00000000)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: BOOT 7f5dffd8 00028 (v01 TOSCPL TOSCPL00 06040000  LTP 00000001)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: SSDT 7f5d80d7 0025F (v01  PmRef  Cpu0Tst 00003000 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: SSDT 7f5d8031 000A6 (v01  PmRef  Cpu1Tst 00003000 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: SSDT 7f5d7b55 004DC (v02  PmRef    CpuPm 00003000 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] 1145MB HIGHMEM available.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] 891MB LOWMEM available.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   mapped low ram: 0 - 37bfe000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   low ram: 0 - 37bfe000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] BRK [0x01b3a000, 0x01b3afff] PGTABLE
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Zone ranges:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   Normal   [mem 0x01000000-0x37bfdfff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   HighMem  [mem 0x37bfe000-0x7f5cffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Movable zone start for each node
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Early memory node ranges
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009cfff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   node   0: [mem 0x00100000-0x7f5cffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] On node 0 totalpages: 521580
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] free_area_init_node: node 0, pgdat c1948b40, node_mem_map f4fb0020
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   DMA zone: 32 pages used for memmap
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   DMA zone: 0 pages reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   DMA zone: 3996 pages, LIFO batch:0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   Normal zone: 1752 pages used for memmap
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   Normal zone: 224254 pages, LIFO batch:31
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   HighMem zone: 2292 pages used for memmap
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]   HighMem zone: 293330 pages, LIFO batch:31
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Using APIC driver default
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x1008
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] nr_irqs_gsi: 40
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dbfff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000dc000-0x000dffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000e3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e4000-0x000fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] e820: [mem 0x80000000-0xdfffffff] available for PCI devices
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] PERCPU: Embedded 14 pages/cpu @f7bd6000 s36288 r0 d21056 u57344
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] pcpu-alloc: s36288 r0 d21056 u57344 alloc=14*4096
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 519796
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=dae33f41-73b2-4804-9829-e92a660ae9ad ro quiet splash vt.handoff=7
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing CPU#0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] allocated 4173432 bytes of page_cgroup
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Initializing HighMem for node 0 (00037bfe:0007f5d0)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Memory: 2036848K/2086320K available (6352K kernel code, 607K rwdata, 2640K rodata, 880K init, 908K bss, 49472K reserved, 1173320K highmem)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] virtual kernel memory layout:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]     fixmap  : 0xfff14000 - 0xfffff000   ( 940 kB)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]     pkmap   : 0xffc00000 - 0xffe00000   (2048 kB)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]     vmalloc : 0xf83fe000 - 0xffbfe000   ( 120 MB)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xf7bfe000   ( 891 MB)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]       .init : 0xc1962000 - 0xc1a3e000   ( 880 kB)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]       .data : 0xc16343a4 - 0xc1961dc0   (3254 kB)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000]       .text : 0xc1000000 - 0xc16343a4   (6352 kB)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Hierarchical RCU implementation.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] NR_IRQS:2304 nr_irqs:512 16
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] CPU 0 irqstacks, hard=f7008000 soft=f700a000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] Console: colour dummy device 80x25
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] console [tty0] enabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] hpet clockevent registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] tsc: Fast TSC calibration failed
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] tsc: PIT calibration matches HPET. 1 loops
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.000000] tsc: Detected 1662.496 MHz processor
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004003] Calibrating delay loop (skipped), value calculated using timer frequency.. 3324.99 BogoMIPS (lpj=6649984)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004012] pid_max: default: 32768 minimum: 301
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004088] Security Framework initialized
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004117] AppArmor: AppArmor initialized
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004122] Yama: becoming mindful.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004230] Mount-cache hash table entries: 512
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004654] Initializing cgroup subsys memory
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004676] Initializing cgroup subsys devices
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004682] Initializing cgroup subsys freezer
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004687] Initializing cgroup subsys blkio
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004692] Initializing cgroup subsys perf_event
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004700] Initializing cgroup subsys hugetlb
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004751] CPU: Physical Processor ID: 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004756] CPU: Processor Core ID: 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004762] mce: CPU supports 5 MCE banks
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004776] CPU0: Thermal monitoring handled by SMI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004798] Last level iTLB entries: 4KB 32, 2MB 0, 4MB 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004798] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 8
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.004798] tlb_flushall_shift: 6
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.005212] Freeing SMP alternatives memory: 28K (c1a3e000 - c1a45000)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.010025] ACPI: Core revision 20130517
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.020171] ACPI: All ACPI Tables successfully acquired
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.023614] ftrace: allocating 27140 entries in 54 pages
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.040165] Enabling APIC mode:  Flat.  Using 1 I/O APICs
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.044151] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.083847] smpboot: CPU0: Intel(R) Atom(TM) CPU N455   @ 1.66GHz (fam: 06, model: 1c, stepping: 0a)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084000] Performance Events: PEBS fmt0+, 8-deep LBR, Atom events, Intel PMU driver.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084000] ... version:                3
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084000] ... bit width:              40
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084000] ... generic registers:      2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084000] ... value mask:             000000ffffffffff
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084000] ... max period:             000000007fffffff
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084000] ... fixed-purpose events:   3
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084000] ... event mask:             0000000700000003
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084212] CPU 1 irqstacks, hard=f70f0000 soft=f70f2000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.084220] smpboot: Booting Node   0, Processors  #1 OK
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.008000] Initializing CPU#1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.008000] CPU0: Thermal monitoring enabled (TM1)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096000] TSC synchronization [CPU#0 -> CPU#1]:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096000] Measured 830000080 cycles TSC warp between CPUs, turning off TSC clock.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096000] tsc: Marking TSC unstable due to check_tsc_sync_source failed
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096114] Brought up 2 CPUs
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096121] smpboot: Total of 2 processors activated (6649.98 BogoMIPS)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096246] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096843] devtmpfs: initialized
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096843] EVM: security.selinux
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096843] EVM: security.SMACK64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096843] EVM: security.capability
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.096843] PM: Registering ACPI NVS region [mem 0x7f5e0000-0x7f5e2fff] (12288 bytes)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.100864] regulator-dummy: no parameters
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.100918] RTC time: 10:56:02, date: 11/30/13
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.101022] NET: Registered protocol family 16
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.101369] EISA bus registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.101521] ACPI: bus type PCI registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.101529] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.101659] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.101668] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.101671] PCI: Using MMCONFIG for extended config space
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.101675] PCI: Using configuration type 1 for base access
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.104177] bio: create slab <bio-0> at 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.104236] ACPI: Added _OSI(Module Device)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.104243] ACPI: Added _OSI(Processor Device)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.104249] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.104254] ACPI: Added _OSI(Processor Aggregator Device)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.107260] ACPI: EC: Look up EC in DSDT
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.116795] ACPI: SSDT 7f5d89a0 00203 (v02  PmRef  Cpu0Ist 00003000 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.117568] ACPI: Dynamic OEM Table Load:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.117576] ACPI: SSDT   (null) 00203 (v02  PmRef  Cpu0Ist 00003000 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.117869] ACPI: SSDT 7f5d8336 005E5 (v02  PmRef  Cpu0Cst 00003001 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.118581] ACPI: Dynamic OEM Table Load:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.118587] ACPI: SSDT   (null) 005E5 (v02  PmRef  Cpu0Cst 00003001 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.119137] ACPI: SSDT 7f5d8ba3 000D4 (v02  PmRef  Cpu1Ist 00003000 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.119871] ACPI: Dynamic OEM Table Load:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.119878] ACPI: SSDT   (null) 000D4 (v02  PmRef  Cpu1Ist 00003000 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.120069] ACPI: SSDT 7f5d891b 00085 (v02  PmRef  Cpu1Cst 00003000 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.120783] ACPI: Dynamic OEM Table Load:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.120790] ACPI: SSDT   (null) 00085 (v02  PmRef  Cpu1Cst 00003000 INTL 20050624)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.124230] ACPI: Interpreter enabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.124249] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130517/hwxface-571)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.124260] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.124294] ACPI: (supports S0 S3 S4 S5)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.124299] ACPI: Using IOAPIC for interrupt routing
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.124365] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.124610] ACPI: No dock devices found.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.196730] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.196894] ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20130517/dsfield-211)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.196910] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f70282a0), AE_ALREADY_EXISTS (20130517/psparse-536)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.196928] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.197092] ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20130517/dsfield-211)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.197106] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f70282a0), AE_ALREADY_EXISTS (20130517/psparse-536)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.197132] acpi PNP0A08:00: ACPI _OSC support notification failed, disabling PCIe ASPM
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.197139] acpi PNP0A08:00: Unable to request _OSC control (_OSC support mask: 0x08)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200448] PCI host bridge to bus 0000:00
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200457] pci_bus 0000:00: root bus resource [bus 00-3f]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200465] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200472] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200478] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200484] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200491] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200497] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200504] pci_bus 0000:00: root bus resource [mem 0x80000000-0xf7ffffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200510] pci_bus 0000:00: root bus resource [io  0x0d00-0xfdff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200531] pci 0000:00:00.0: [8086:a010] type 00 class 0x060000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200738] pci 0000:00:02.0: [8086:a011] type 00 class 0x030000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200758] pci 0000:00:02.0: reg 0x10: [mem 0xf0200000-0xf027ffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200770] pci 0000:00:02.0: reg 0x14: [io  0x18d0-0x18d7]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200781] pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200792] pci 0000:00:02.0: reg 0x1c: [mem 0xf0000000-0xf00fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.200984] pci 0000:00:02.1: [8086:a012] type 00 class 0x038000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.201001] pci 0000:00:02.1: reg 0x10: [mem 0xf0280000-0xf02fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.201254] pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.201285] pci 0000:00:1b.0: reg 0x10: [mem 0xf0300000-0xf0303fff 64bit]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.201388] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.201570] pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.201678] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.201794] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.201887] pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.201996] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.202112] pci 0000:00:1c.1: System wakeup disabled by ACPI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.202206] pci 0000:00:1c.2: [8086:27d4] type 01 class 0x060400
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.202316] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.202505] pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.202567] pci 0000:00:1d.0: reg 0x20: [io  0x1820-0x183f]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.202742] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.202834] pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.202898] pci 0000:00:1d.1: reg 0x20: [io  0x1840-0x185f]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203030] pci 0000:00:1d.1: System wakeup disabled by ACPI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203120] pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203183] pci 0000:00:1d.2: reg 0x20: [io  0x1860-0x187f]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203349] pci 0000:00:1d.2: System wakeup disabled by ACPI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203437] pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203500] pci 0000:00:1d.3: reg 0x20: [io  0x1880-0x189f]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203632] pci 0000:00:1d.3: System wakeup disabled by ACPI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203736] pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203769] pci 0000:00:1d.7: reg 0x10: [mem 0xf0504000-0xf05043ff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.203891] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204029] pci 0000:00:1d.7: System wakeup disabled by ACPI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204125] pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204297] pci 0000:00:1e.0: System wakeup disabled by ACPI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204389] pci 0000:00:1f.0: [8086:27bc] type 00 class 0x060100
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204495] pci 0000:00:1f.0: [Firmware Bug]: TigerPoint LPC.BM_STS cleared
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204707] pci 0000:00:1f.2: [8086:27c1] type 00 class 0x010601
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204736] pci 0000:00:1f.2: reg 0x10: [io  0x18e8-0x18ef]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204751] pci 0000:00:1f.2: reg 0x14: [io  0x18dc-0x18df]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204767] pci 0000:00:1f.2: reg 0x18: [io  0x18e0-0x18e7]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204781] pci 0000:00:1f.2: reg 0x1c: [io  0x18d8-0x18db]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204796] pci 0000:00:1f.2: reg 0x20: [io  0x18c0-0x18cf]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204811] pci 0000:00:1f.2: reg 0x24: [mem 0xf0504400-0xf05047ff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.204870] pci 0000:00:1f.2: PME# supported from D3hot
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.205051] pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.205123] pci 0000:00:1f.3: reg 0x20: [io  0x18a0-0x18bf]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.205427] pci 0000:00:1c.0: PCI bridge to [bus 05]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.205438] pci 0000:00:1c.0:   bridge window [io  0x0000-0x0fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.205604] pci 0000:07:00.0: [168c:002b] type 00 class 0x028000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.205646] pci 0000:07:00.0: reg 0x10: [mem 0xf0100000-0xf010ffff 64bit]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.205791] pci 0000:07:00.0: supports D1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.205797] pci 0000:07:00.0: PME# supported from D0 D1 D3hot
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212039] pci 0000:00:1c.1: PCI bridge to [bus 07]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212053] pci 0000:00:1c.1:   bridge window [mem 0xf0100000-0xf01fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212266] pci 0000:09:00.0: [10ec:8136] type 00 class 0x020000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212337] pci 0000:09:00.0: reg 0x10: [io  0x2000-0x20ff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212452] pci 0000:09:00.0: reg 0x18: [mem 0xf050c000-0xf050cfff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212521] pci 0000:09:00.0: reg 0x20: [mem 0xf0508000-0xf050bfff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212766] pci 0000:09:00.0: supports D1 D2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212772] pci 0000:09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212054] pci 0000:09:00.0: System wakeup disabled by ACPI
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212238] pci 0000:00:1c.2: PCI bridge to [bus 09]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212249] pci 0000:00:1c.2:   bridge window [io  0x2000-0x2fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212264] pci 0000:00:1c.2:   bridge window [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212400] pci 0000:00:1e.0: PCI bridge to [bus 11] (subtractive decode)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212418] pci 0000:00:1e.0:   bridge window [io  0x0000-0x0cf7] (subtractive decode)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212425] pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212432] pci 0000:00:1e.0:   bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212438] pci 0000:00:1e.0:   bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212445] pci 0000:00:1e.0:   bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212451] pci 0000:00:1e.0:   bridge window [mem 0x000e0000-0x000e3fff] (subtractive decode)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212458] pci 0000:00:1e.0:   bridge window [mem 0x80000000-0xf7ffffff] (subtractive decode)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212465] pci 0000:00:1e.0:   bridge window [io  0x0d00-0xfdff] (subtractive decode)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.212495] pci_bus 0000:00: on NUMA node 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.232188] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 10 11 12 14 15)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.232358] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.232524] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.232689] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.232864] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.233040] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.233216] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.233390] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.234052] ACPI: Enabled 2 GPEs in block 00 to 1F
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.234072] ACPI: \_SB_.PCI0: notify handler is installed
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.234180] Found 1 acpi root devices
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.234284] ACPI: EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.234497] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.234497] vgaarb: loaded
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.234497] vgaarb: bridge control possible 0000:00:02.0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.234497] SCSI subsystem initialized
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.234497] ACPI: bus type ATA registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.236041] libata version 3.00 loaded.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.236096] ACPI: bus type USB registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.236150] usbcore: registered new interface driver usbfs
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.236176] usbcore: registered new interface driver hub
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.236194] usbcore: registered new device driver usb
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.236194] PCI: Using ACPI for IRQ routing
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244174] PCI: pci_cache_line_size set to 64 bytes
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244226] pci 0000:00:1d.7: address space collision: [mem 0xf0504000-0xf05043ff] conflicts with PCI Bus 0000:09 [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244245] pci 0000:00:1f.2: address space collision: [mem 0xf0504400-0xf05047ff] conflicts with PCI Bus 0000:09 [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244286] e820: reserve RAM buffer [mem 0x0009dc00-0x0009ffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244293] e820: reserve RAM buffer [mem 0x7f5d0000-0x7fffffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244534] NetLabel: Initializing
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244540] NetLabel:  domain hash size = 128
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244544] NetLabel:  protocols = UNLABELED CIPSOv4
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244567] NetLabel:  unlabeled traffic allowed by default
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244609] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244609] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.244609] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.246225] Switched to clocksource hpet
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259120] AppArmor: AppArmor Filesystem Enabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259191] pnp: PnP ACPI init
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259228] ACPI: bus type PNP registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259718] system 00:00: [io  0x0800-0x080f] has been reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259729] system 00:00: [io  0x1000-0x107f] could not be reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259737] system 00:00: [io  0x1180-0x11bf] has been reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259745] system 00:00: [io  0x04d0-0x04d1] has been reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259752] system 00:00: [io  0xfe00] has been reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259759] system 00:00: [io  0x164e-0x174c] has been reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259768] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259775] system 00:00: [mem 0xfed14000-0xfed17fff] has been reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259783] system 00:00: [mem 0xf8000000-0xfbffffff] has been reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259790] system 00:00: [mem 0xfef00000-0xfeffffff] has been reserved
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259801] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259834] pnp 00:01: [dma 4]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259892] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.259984] pnp 00:02: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.260169] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.260243] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.280154] pnp 00:05: Plug and Play ACPI device, IDs PNP0303 (active)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.280249] pnp 00:06: Plug and Play ACPI device, IDs TOS0100 SYN0700 SYN0002 PNP0f13 (active)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.280711] pnp: PnP ACPI: found 7 devices
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.280716] ACPI: bus type PNP unregistered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.280724] PnPBIOS: Disabled by ACPI PNP
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321281] pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 05] add_size 1000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321295] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 05] add_size 200000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321303] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 05] add_size 200000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321320] pci 0000:00:1c.1: bridge window [io  0x1000-0x0fff] to [bus 07] add_size 1000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321329] pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 07] add_size 200000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321346] pci 0000:00:1c.2: bridge window [mem 0x00100000-0x000fffff] to [bus 09] add_size 400000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321375] pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321383] pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321390] pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321398] pci 0000:00:1c.2: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 400000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321405] pci 0000:00:1c.0: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321412] pci 0000:00:1c.1: res[13]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321426] pci 0000:00:1c.0: BAR 14: assigned [mem 0x80000000-0x801fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321437] pci 0000:00:1c.0: BAR 15: assigned [mem 0x80200000-0x803fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321447] pci 0000:00:1c.1: BAR 15: assigned [mem 0x80400000-0x805fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321457] pci 0000:00:1c.2: BAR 14: assigned [mem 0x80600000-0x809fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321468] pci 0000:00:1c.0: BAR 13: assigned [io  0x3000-0x3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321477] pci 0000:00:1c.1: BAR 13: assigned [io  0x4000-0x4fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321487] pci 0000:00:1d.7: BAR 0: assigned [mem 0x80a00000-0x80a003ff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321502] pci 0000:00:1f.2: BAR 5: assigned [mem 0x80a00400-0x80a007ff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321513] pci 0000:00:1c.0: PCI bridge to [bus 05]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321521] pci 0000:00:1c.0:   bridge window [io  0x3000-0x3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321531] pci 0000:00:1c.0:   bridge window [mem 0x80000000-0x801fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321541] pci 0000:00:1c.0:   bridge window [mem 0x80200000-0x803fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321552] pci 0000:00:1c.1: PCI bridge to [bus 07]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321559] pci 0000:00:1c.1:   bridge window [io  0x4000-0x4fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321569] pci 0000:00:1c.1:   bridge window [mem 0xf0100000-0xf01fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321579] pci 0000:00:1c.1:   bridge window [mem 0x80400000-0x805fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321590] pci 0000:00:1c.2: PCI bridge to [bus 09]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321597] pci 0000:00:1c.2:   bridge window [io  0x2000-0x2fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321607] pci 0000:00:1c.2:   bridge window [mem 0x80600000-0x809fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321616] pci 0000:00:1c.2:   bridge window [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321628] pci 0000:00:1e.0: PCI bridge to [bus 11]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321650] pci 0000:00:1c.0: enabling device (0000 -> 0003)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321987] pci 0000:00:1e.0: setting latency timer to 64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.321997] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322004] pci_bus 0000:00: resource 5 [mem 0x000a0000-0x000bffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322011] pci_bus 0000:00: resource 6 [mem 0x000d0000-0x000d3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322017] pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d7fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322024] pci_bus 0000:00: resource 8 [mem 0x000d8000-0x000dbfff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322030] pci_bus 0000:00: resource 9 [mem 0x000e0000-0x000e3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322037] pci_bus 0000:00: resource 10 [mem 0x80000000-0xf7ffffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322043] pci_bus 0000:00: resource 11 [io  0x0d00-0xfdff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322050] pci_bus 0000:05: resource 0 [io  0x3000-0x3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322057] pci_bus 0000:05: resource 1 [mem 0x80000000-0x801fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322064] pci_bus 0000:05: resource 2 [mem 0x80200000-0x803fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322070] pci_bus 0000:07: resource 0 [io  0x4000-0x4fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322077] pci_bus 0000:07: resource 1 [mem 0xf0100000-0xf01fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322083] pci_bus 0000:07: resource 2 [mem 0x80400000-0x805fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322090] pci_bus 0000:09: resource 0 [io  0x2000-0x2fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322097] pci_bus 0000:09: resource 1 [mem 0x80600000-0x809fffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322103] pci_bus 0000:09: resource 2 [mem 0xf0500000-0xf05fffff 64bit pref]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322111] pci_bus 0000:11: resource 4 [io  0x0000-0x0cf7]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322117] pci_bus 0000:11: resource 5 [mem 0x000a0000-0x000bffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322124] pci_bus 0000:11: resource 6 [mem 0x000d0000-0x000d3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322130] pci_bus 0000:11: resource 7 [mem 0x000d4000-0x000d7fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322136] pci_bus 0000:11: resource 8 [mem 0x000d8000-0x000dbfff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322143] pci_bus 0000:11: resource 9 [mem 0x000e0000-0x000e3fff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322150] pci_bus 0000:11: resource 10 [mem 0x80000000-0xf7ffffff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322156] pci_bus 0000:11: resource 11 [io  0x0d00-0xfdff]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322227] NET: Registered protocol family 2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322557] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322622] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322679] TCP: Hash tables configured (established 8192 bind 8192)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322722] TCP: reno registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322729] UDP hash table entries: 512 (order: 2, 16384 bytes)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322746] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322891] NET: Registered protocol family 1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.322932] pci 0000:00:02.0: Boot video device
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.323945] PCI: CLS 32 bytes, default 64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    0.324132] Trying to unpack rootfs image as initramfs...
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.052327] Freeing initrd memory: 16544K (f5fa0000 - f6fc8000)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.052461] Simple Boot Flag at 0x35 set to 0x1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.052732] Scanning for low memory corruption every 60 seconds
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.053298] Initialise module verification
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.053405] audit: initializing netlink socket (disabled)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.053429] type=2000 audit(1385808963.052:1): initialized
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.106334] bounce pool size: 64 pages
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.106370] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.109820] zbud: loaded
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.109968] VFS: Disk quotas dquot_6.5.2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.110093] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.111404] fuse init (API version 7.22)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.111634] msgmni has been set to 1718
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.112823] Key type asymmetric registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.112832] Asymmetric key parser 'x509' registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.112943] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.113034] io scheduler noop registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.113042] io scheduler deadline registered (default)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.113121] io scheduler cfq registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.113389] pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.113536] pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.113663] pcieport 0000:00:1c.2: irq 42 for MSI/MSI-X
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.113821] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.113861] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.114026] intel_idle: MWAIT substates: 0x20220
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.114044] intel_idle: v0.4 model 0x1C
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.114050] intel_idle: lapic_timer_reliable_states 0x2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.114719] ACPI: AC Adapter [ACAD] (on-line)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.115167] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0d/PNP0C0D:00/input/input0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.115298] ACPI: Lid Switch [LID0]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.115409] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0A08:00/PNP0C0C:00/input/input1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.115419] ACPI: Power Button [PWRB]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.115515] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.115523] ACPI: Power Button [PWRF]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.115664] ACPI: Requesting acpi_cpufreq
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.120410] GHES: HEST is not enabled!
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.120632] isapnp: Scanning for PnP cards...
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.124203] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.128507] Linux agpgart interface v0.103
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.128677] agpgart-intel 0000:00:00.0: Intel GMA3150 Chipset
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.128820] agpgart-intel 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.129008] agpgart-intel 0000:00:00.0: detected 8192K stolen memory
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.129238] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.133877] brd: module loaded
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.136292] loop: module loaded
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.137609] libphy: Fixed MDIO Bus: probed
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.137938] tun: Universal TUN/TAP device driver, 1.6
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.137943] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.138073] PPP generic driver version 2.4.2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.138204] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.138211] ehci-pci: EHCI PCI platform driver
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.138422] ehci-pci 0000:00:1d.7: setting latency timer to 64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.138446] ehci-pci 0000:00:1d.7: EHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.138464] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.138490] ehci-pci 0000:00:1d.7: debug port 1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.142430] ehci-pci 0000:00:1d.7: cache line size of 32 is not supported
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.144149] ehci-pci 0000:00:1d.7: irq 23, io mem 0x80a00000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.156038] ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.156115] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.156125] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.156132] usb usb1: Product: EHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.156140] usb usb1: Manufacturer: Linux 3.11.0-13-generic ehci_hcd
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.156147] usb usb1: SerialNumber: 0000:00:1d.7
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.156477] hub 1-0:1.0: USB hub found
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.156492] hub 1-0:1.0: 8 ports detected
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157384] ehci-platform: EHCI generic platform driver
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157417] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157423] ohci-platform: OHCI generic platform driver
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157450] uhci_hcd: USB Universal Host Controller Interface driver
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157631] uhci_hcd 0000:00:1d.0: setting latency timer to 64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157642] uhci_hcd 0000:00:1d.0: UHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157659] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157705] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001820
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157792] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157801] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157809] usb usb2: Product: UHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157816] usb usb2: Manufacturer: Linux 3.11.0-13-generic uhci_hcd
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.157824] usb usb2: SerialNumber: 0000:00:1d.0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158127] hub 2-0:1.0: USB hub found
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158142] hub 2-0:1.0: 2 ports detected
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158493] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158504] uhci_hcd 0000:00:1d.1: UHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158521] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158598] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001840
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158683] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158692] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158700] usb usb3: Product: UHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158708] usb usb3: Manufacturer: Linux 3.11.0-13-generic uhci_hcd
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.158715] usb usb3: SerialNumber: 0000:00:1d.1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159016] hub 3-0:1.0: USB hub found
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159031] hub 3-0:1.0: 2 ports detected
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159484] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159495] uhci_hcd 0000:00:1d.2: UHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159512] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159586] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001860
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159676] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159685] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159693] usb usb4: Product: UHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159701] usb usb4: Manufacturer: Linux 3.11.0-13-generic uhci_hcd
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.159708] usb usb4: SerialNumber: 0000:00:1d.2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160056] hub 4-0:1.0: USB hub found
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160071] hub 4-0:1.0: 2 ports detected
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160483] uhci_hcd 0000:00:1d.3: setting latency timer to 64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160494] uhci_hcd 0000:00:1d.3: UHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160511] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160586] uhci_hcd 0000:00:1d.3: irq 16, io base 0x00001880
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160672] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160681] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160689] usb usb5: Product: UHCI Host Controller
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160697] usb usb5: Manufacturer: Linux 3.11.0-13-generic uhci_hcd
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.160704] usb usb5: SerialNumber: 0000:00:1d.3
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.161013] hub 5-0:1.0: USB hub found
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.161027] hub 5-0:1.0: 2 ports detected
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.161540] i8042: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.193974] serio: i8042 KBD port at 0x60,0x64 irq 1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.194003] serio: i8042 AUX port at 0x60,0x64 irq 12
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.194357] mousedev: PS/2 mouse device common for all mice
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.197746] rtc_cmos 00:03: RTC can wake from S4
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.197972] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.198019] rtc_cmos 00:03: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.198216] device-mapper: uevent: version 1.0.3
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.198416] device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised: dm-devel@redhat.com
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.198481] platform eisa.0: Probing EISA bus 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.198516] platform eisa.0: EISA: Detected 0 cards
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.198534] cpufreq-nforce2: No nForce2 chipset.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.198665] cpuidle: using governor ladder
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.198830] cpuidle: using governor menu
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.198863] ledtrig-cpu: registered to indicate activity on CPUs
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.199104] TCP: cubic registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.199419] NET: Registered protocol family 10
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.199956] NET: Registered protocol family 17
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.199994] Key type dns_resolver registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.200494] Using IPI No-Shortcut mode
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.200737] PM: Hibernation image not present or could not be loaded.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.200748] Loading module verification certificates
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.214469] MODSIGN: Loaded cert 'Magrathea: Glacier signing key: 121c3931998f688796d5ac98c50cd636878ded2d'
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.214504] registered taskstats version 1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.221830] Key type trusted registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.228519] Key type encrypted registered
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.235744] AppArmor: AppArmor sha1 policy hashing enabled
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.236462]   Magic number: 5:237:933
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.236607] rtc_cmos 00:03: setting system clock to 2013-11-30 10:56:04 UTC (1385808964)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.237578] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.237586] EDD information not available.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.239863] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.352469] [Firmware Bug]: battery: (dis)charge rate invalid.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.352544] ACPI: Battery Slot [BAT1] (battery present)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.474557] isapnp: No Plug & Play device found
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.475208] Freeing unused kernel memory: 880K (c1962000 - c1a3e000)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.475325] Write protecting the kernel text: 6356k
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.475468] Write protecting the kernel read-only data: 2644k
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.475473] NX-protecting the kernel data: 5932k
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.603030] mii: module verification failed: signature and/or required key missing - tainting kernel
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.618718] ahci 0000:00:1f.2: version 3.0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.618967] ahci 0000:00:1f.2: irq 43 for MSI/MSI-X
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.619095] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.619108] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part 
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.619120] ahci 0000:00:1f.2: setting latency timer to 64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.623220] scsi0 : ahci
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.625952] scsi1 : ahci
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.628960] scsi2 : ahci
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.629819] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.629855] r8169 0000:09:00.0: can't disable ASPM; OS doesn't have ASPM control
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.630202] r8169 0000:09:00.0: irq 44 for MSI/MSI-X
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.630717] r8169 0000:09:00.0 eth0: RTL8168e/8111e at 0xf8422000, 88:ae:1d:f4:54:83, XID 0c200000 IRQ 44
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.630730] r8169 0000:09:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.632285] scsi3 : ahci
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.632509] ata1: SATA max UDMA/133 abar m1024@0x80a00400 port 0x80a00500 irq 43
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.632517] ata2: SATA max UDMA/133 abar m1024@0x80a00400 port 0x80a00580 irq 43
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.632523] ata3: SATA max UDMA/133 abar m1024@0x80a00400 port 0x80a00600 irq 43
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.632529] ata4: SATA max UDMA/133 abar m1024@0x80a00400 port 0x80a00680 irq 43
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.728116] usb 1-4: new high-speed USB device number 3 using ehci-pci
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.952133] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.952169] ata3: SATA link down (SStatus 0 SControl 300)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.952201] ata2: SATA link down (SStatus 0 SControl 300)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.952232] ata4: SATA link down (SStatus 0 SControl 300)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.953251] ata1.00: ATA-8: Hitachi HTS545025B9A300, PB2OC64G, max UDMA/133
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.953264] ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.954522] ata1.00: configured for UDMA/133
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.954886] scsi 0:0:0:0: Direct-Access     ATA      Hitachi HTS54502 PB2O PQ: 0 ANSI: 5
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.955466] sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.955582] sd 0:0:0:0: Attached scsi generic sg0 type 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.955713] sd 0:0:0:0: [sda] Write Protect is off
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.955725] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    1.955863] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.002791]  sda: sda1 sda2 sda3 < sda5 sda6 >
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.004245] sd 0:0:0:0: [sda] Attached SCSI disk
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.116133] usb 1-4: New USB device found, idVendor=0bda, idProduct=0138
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.116144] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.116150] usb 1-4: Product: USB2.0-CRW
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.116156] usb 1-4: Manufacturer: Generic
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.116162] usb 1-4: SerialNumber: 20090516388200000
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.232098] usb 1-8: new high-speed USB device number 4 using ehci-pci
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.368906] usb 1-8: New USB device found, idVendor=090c, idProduct=037b
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.368922] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.368933] usb 1-8: Product: USB 2.0 Camera
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.368943] usb 1-8: Manufacturer: Image Processor
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.368952] usb 1-8: SerialNumber: USB 2.0 Camera
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.374331] usbcore: registered new interface driver usb-storage
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.388465] ums-realtek 1-4:1.0: USB Mass Storage device detected
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.404098] scsi4 : usb-storage 1-4:1.0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.404350] usbcore: registered new interface driver ums-realtek
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.608055] usb 2-2: new full-speed USB device number 2 using uhci_hcd
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.728118] usb 2-2: device descriptor read/64, error -71
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.805233] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    2.952070] usb 2-2: device descriptor read/64, error -71
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    3.168067] usb 2-2: new full-speed USB device number 3 using uhci_hcd
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    3.288103] usb 2-2: device descriptor read/64, error -71
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    3.407153] scsi 4:0:0:0: Direct-Access     Generic- Multi-Card       1.00 PQ: 0 ANSI: 0 CCS
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    3.407743] sd 4:0:0:0: Attached scsi generic sg1 type 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    3.413724] sd 4:0:0:0: [sdb] Attached SCSI removable disk
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    3.512098] usb 2-2: device descriptor read/64, error -71
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    3.728081] usb 2-2: new full-speed USB device number 4 using uhci_hcd
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    4.136082] usb 2-2: device not accepting address 4, error -71
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    4.248105] usb 2-2: new full-speed USB device number 5 using uhci_hcd
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    4.656088] usb 2-2: device not accepting address 5, error -71
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [    4.656133] hub 2-0:1.0: unable to enumerate USB device on port 2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   10.524231] Adding 2084860k swap on /dev/sda5.  Priority:-1 extents:1 across:2084860k FS
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   10.636408] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.084159] lp: driver loaded but no devices found
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.174821] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.547667] wmi: Mapper loaded
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.683093] [drm] Initialized drm 1.1.0 20060810
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.742399] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.742611] input: Toshiba input device as /devices/virtual/input/input4
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.779576] cfg80211: Calling CRDA to update world regulatory domain
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.884066] [drm] Memory usable by graphics device = 512M
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.884476] i915 0000:00:02.0: setting latency timer to 64
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.887771] i915 0000:00:02.0: irq 45 for MSI/MSI-X
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.887807] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.887814] [drm] Driver supports precise vblank timestamp query.
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   11.887942] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.081425] [drm] initialized overlay support
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.446446] microcode: CPU0 sig=0x106ca, pf=0x4, revision=0x107
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.553136] fbcon: inteldrmfb (fb0) is primary device
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.676782] ath: phy0: ASPM enabled: 0x43
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.676788] ath: EEPROM regdomain: 0x65
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.676790] ath: EEPROM indicates we should expect a direct regpair map
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.676795] ath: Country alpha2 being used: 00
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.676797] ath: Regpair used: 0x65
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.700375] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.702258] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf8880000, irq=17
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.726879] type=1400 audit(1385805375.986:2): apparmor="STATUS" operation="profile_load" parent=395 profile="unconfined" name="/sbin/dhclient" pid=404 comm="apparmor_parser"
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.726900] type=1400 audit(1385805375.986:3): apparmor="STATUS" operation="profile_load" parent=395 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=404 comm="apparmor_parser"
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.726916] type=1400 audit(1385805375.986:4): apparmor="STATUS" operation="profile_load" parent=395 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=404 comm="apparmor_parser"
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.733441] type=1400 audit(1385805375.994:5): apparmor="STATUS" operation="profile_replace" parent=395 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=404 comm="apparmor_parser"
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.733463] type=1400 audit(1385805375.994:6): apparmor="STATUS" operation="profile_replace" parent=395 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=404 comm="apparmor_parser"
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.734777] type=1400 audit(1385805375.994:7): apparmor="STATUS" operation="profile_replace" parent=395 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=404 comm="apparmor_parser"
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.759295] Console: switching to colour frame buffer device 128x37
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.771426] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.771435] i915 0000:00:02.0: registered panic notifier
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.779748] type=1400 audit(1385805376.038:8): apparmor="STATUS" operation="profile_load" parent=395 profile="unconfined" name="/usr/sbin/ntpd" pid=423 comm="apparmor_parser"
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.810790] acpi device:01: registered as cooling_device2
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.810906] ACPI: Video Device [IGD0] (multi-head: yes  rom: no  post: no)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.811195] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.811699] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.812275] ACPI Warning: 0x00001028-0x0000102f SystemIO conflicts with Region \_SB_.PCI0.LPC0.PMIO 1 (20130517/utaddress-251)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.812296] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.812307] ACPI Warning: 0x000011b0-0x000011bf SystemIO conflicts with Region \_SB_.PCI0.LPC0.GPIO 1 (20130517/utaddress-251)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.812324] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.812398] ACPI Warning: 0x00001180-0x000011af SystemIO conflicts with Region \_SB_.PCI0.LPC0.GPIO 1 (20130517/utaddress-251)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.812414] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.812421] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.812914] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.872798] SKU: Nid=0x1d sku_cfg=0x4017992d
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.872806] SKU: port_connectivity=0x1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.872811] SKU: enable_pcbeep=0x1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.872816] SKU: check_sum=0x00000007
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.872820] SKU: customization=0x00000099
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.872825] SKU: external_amp=0x5
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.872829] SKU: platform_type=0x1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.872834] SKU: swap=0x0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.872838] SKU: override=0x1
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.873349] autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.873358]    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.873365]    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.873370]    mono: mono_out=0x0
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.873375]    inputs:
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.873381]      Internal Mic=0x19
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.873388]      Mic=0x18
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.873395] realtek: No valid SSID, checking pincfg 0x4017992d for NID 0x1d
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.873401] realtek: Enabling init ASM_ID=0x992d CODEC_ID=10ec0269
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.923800] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.932272] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   12.940729] Linux video capture interface: v2.00
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.340464] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (090c:037b)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.456080] input: USB 2.0 Camera as /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/input/input8
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.471314] usbcore: registered new interface driver uvcvideo
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.471323] USB Video Class driver (1.1.1)
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.704110] Bluetooth: Core ver 2.16
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.712316] NET: Registered protocol family 31
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.712327] Bluetooth: HCI device and connection manager initialized
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.712349] Bluetooth: HCI socket layer initialized
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.712363] Bluetooth: L2CAP socket layer initialized
Nov 30 10:56:16 nava-TOSHIBA-NB250 kernel: [   13.712393] Bluetooth: SCO socket layer initialized
Nov 30 10:56:17 nava-TOSHIBA-NB250 kernel: [   13.817852] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Nov 30 10:56:17 nava-TOSHIBA-NB250 kernel: [   13.817864] Bluetooth: BNEP filters: protocol multicast
Nov 30 10:56:17 nava-TOSHIBA-NB250 kernel: [   13.817889] Bluetooth: BNEP socket layer initialized
Nov 30 10:56:17 nava-TOSHIBA-NB250 kernel: [   13.837422] Bluetooth: RFCOMM TTY layer initialized
Nov 30 10:56:17 nava-TOSHIBA-NB250 kernel: [   13.837452] Bluetooth: RFCOMM socket layer initialized
Nov 30 10:56:17 nava-TOSHIBA-NB250 kernel: [   13.837460] Bluetooth: RFCOMM ver 1.11
Nov 30 10:56:17 nava-TOSHIBA-NB250 kernel: [   14.074037] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04733/0xa40000/0xa0000, board id: 3655, fw id: 528321
Nov 30 10:56:17 nava-TOSHIBA-NB250 kernel: [   14.190262] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input9
Nov 30 10:56:17 nava-TOSHIBA-NB250 kernel: [   14.408128] ppdev: user-space parallel port driver
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.828196] microcode: CPU1 sig=0x106ca, pf=0x4, revision=0x107
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.913398] type=1400 audit(1385805378.174:9): apparmor="STATUS" operation="profile_load" parent=517 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=541 comm="apparmor_parser"
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.913430] type=1400 audit(1385805378.174:10): apparmor="STATUS" operation="profile_load" parent=517 profile="unconfined" name="/usr/sbin/cupsd" pid=541 comm="apparmor_parser"
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.929378] type=1400 audit(1385805378.190:11): apparmor="STATUS" operation="profile_replace" parent=517 profile="unconfined" name="/usr/sbin/cupsd" pid=541 comm="apparmor_parser"
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.949384] cfg80211: World regulatory domain updated:
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.949395] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.949403] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.949410] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.949417] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.949424] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   14.949431] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 30 10:56:18 nava-TOSHIBA-NB250 kernel: [   15.200584] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov 30 10:56:20 nava-TOSHIBA-NB250 modem-manager[659]: <info>  ModemManager (version 0.6.0.0) starting...
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'X22X'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Sierra'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Option'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Huawei'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Ericsson MBM'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Nokia'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Wavecom'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Longcheer'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Linktop'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'MotoC'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Novatel'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Option High-Speed'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'SimTech'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'ZTE'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'AnyData'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Samsung'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Gobi'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Cinterion'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Iridium'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Loaded plugin 'Generic'
Nov 30 10:56:21 nava-TOSHIBA-NB250 modem-manager[659]: <info>  Successfully loaded 20 plugins
Nov 30 10:56:21 nava-TOSHIBA-NB250 NetworkManager[691]: <info> NetworkManager (version 0.9.8.0) is starting...
Nov 30 10:56:21 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Nov 30 10:56:21 nava-TOSHIBA-NB250 NetworkManager[691]: <info> WEXT support is enabled
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]: <info> DNS: loaded plugin dnsmasq
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: init!
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: update_system_hostname
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPluginIfupdown: management mode: unmanaged
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:07:00.0/net/wlan0, iface: wlan0)
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:07:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0/net/eth0, iface: eth0)
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0/net/eth0, iface: eth0): no ifupdown configuration found.
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: end _init.
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ofono: Acquired D-Bus service com.canonical.NMOfono
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ofono: init!
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ofono: end _init.
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Loaded plugin (null): (null)
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    Ifupdown: get unmanaged devices count: 0
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: (152571032) ... get_connections.
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ifupdown: (152571032) ... get_connections (managed=false): return empty list.
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    keyfile: parsing Priya 2 ... 
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    keyfile:     read connection 'Priya 2'
Nov 30 10:56:22 nava-TOSHIBA-NB250 NetworkManager[691]:    keyfile: parsing FRITZ!Box WLAN 3370 ... 
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]:    keyfile:     read connection 'FRITZ!Box WLAN 3370'
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]:    keyfile: parsing Priya ... 
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]:    keyfile:     read connection 'Priya'
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]:    keyfile: parsing Priya 1 ... 
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]:    keyfile:     read connection 'Priya 1'
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ofono: (152486352) ... get_connections.
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]:    SCPlugin-Ofono: (152486352) connections count: 0
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]:    Ifupdown: get unmanaged devices count: 0
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> modem-manager is now available
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> monitoring kernel firmware directory '/lib/firmware'.
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:07:00.0/ieee80211/phy0/rfkill0) (driver ath9k)
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> WiFi hardware radio set enabled
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> WiFi enabled by radio killswitch; enabled by state file
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Networking is enabled by state file
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): using nl80211 for WiFi device control
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): driver supports Access Point (AP) mode
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): bringing up device.
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): preparing device.
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): deactivating device (reason 'managed') [2]
Nov 30 10:56:23 nava-TOSHIBA-NB250 kernel: [   20.165430] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 30 10:56:23 nava-TOSHIBA-NB250 kernel: [   20.166291] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <warn> failed to allocate link cache: (-10) Operation not supported
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (eth0): carrier is OFF
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (eth0): bringing up device.
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (eth0): preparing device.
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (eth0): deactivating device (reason 'managed') [2]
Nov 30 10:56:23 nava-TOSHIBA-NB250 kernel: [   20.389248] r8169 0000:09:00.0 eth0: link down
Nov 30 10:56:23 nava-TOSHIBA-NB250 kernel: [   20.389324] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 30 10:56:23 nava-TOSHIBA-NB250 kernel: [   20.390466] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Added default wired connection '1. vezetékes kapcsolat' for /sys/devices/pci0000:00/0000:00:1c.2/0000:09:00.0/net/eth0
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> wpa_supplicant started
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0) supports 4 scan SSIDs
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <warn> Trying to remove a non-existant call id.
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): supplicant interface state: starting -> ready
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): supplicant interface state: ready -> inactive
Nov 30 10:56:23 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0) supports 4 scan SSIDs
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Auto-activating connection 'Priya'.
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) starting connection 'Priya'
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0/wireless): connection 'Priya' has security, and secrets exist.  No new secrets needed.
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Config: added 'ssid' value 'Priya'
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Config: added 'scan_ssid' value '1'
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Config: added 'auth_alg' value 'OPEN'
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Config: added 'psk' value '<omitted>'
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Config: set interface ap_scan to 1
Nov 30 10:56:24 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): supplicant interface state: inactive -> scanning
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.565998] type=1400 audit(1385805384.826:12): apparmor="STATUS" operation="profile_replace" parent=830 profile="unconfined" name="/sbin/dhclient" pid=833 comm="apparmor_parser"
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.566030] type=1400 audit(1385805384.826:13): apparmor="STATUS" operation="profile_replace" parent=830 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=833 comm="apparmor_parser"
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.566085] type=1400 audit(1385805384.826:14): apparmor="STATUS" operation="profile_replace" parent=830 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=833 comm="apparmor_parser"
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.568791] type=1400 audit(1385805384.830:15): apparmor="STATUS" operation="profile_load" parent=830 profile="unconfined" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=832 comm="apparmor_parser"
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.568820] type=1400 audit(1385805384.830:16): apparmor="STATUS" operation="profile_load" parent=830 profile="unconfined" name="chromium_browser" pid=832 comm="apparmor_parser"
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.569516] type=1400 audit(1385805384.830:17): apparmor="STATUS" operation="profile_replace" parent=830 profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=833 comm="apparmor_parser"
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.569540] type=1400 audit(1385805384.830:18): apparmor="STATUS" operation="profile_replace" parent=830 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=833 comm="apparmor_parser"
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.570964] type=1400 audit(1385805384.830:19): apparmor="STATUS" operation="profile_replace" parent=830 profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=833 comm="apparmor_parser"
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.570994] type=1400 audit(1385805384.830:20): apparmor="STATUS" operation="profile_replace" parent=830 profile="unconfined" name="chromium_browser" pid=832 comm="apparmor_parser"
Nov 30 10:56:24 nava-TOSHIBA-NB250 kernel: [   21.594194] type=1400 audit(1385805384.854:21): apparmor="STATUS" operation="profile_replace" parent=830 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=836 comm="apparmor_parser"
Nov 30 10:56:25 nava-TOSHIBA-NB250 kernel: [   22.249557] wlan0: authenticate with 94:0c:6d:fe:84:60
Nov 30 10:56:25 nava-TOSHIBA-NB250 wpa_supplicant[703]: wlan0: SME: Trying to authenticate with 94:0c:6d:fe:84:60 (SSID='Priya' freq=2412 MHz)
Nov 30 10:56:25 nava-TOSHIBA-NB250 kernel: [   22.281688] wlan0: send auth to 94:0c:6d:fe:84:60 (try 1/3)
Nov 30 10:56:25 nava-TOSHIBA-NB250 kernel: [   22.283716] wlan0: authenticated
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Nov 30 10:56:25 nava-TOSHIBA-NB250 wpa_supplicant[703]: wlan0: Trying to associate with 94:0c:6d:fe:84:60 (SSID='Priya' freq=2412 MHz)
Nov 30 10:56:25 nava-TOSHIBA-NB250 kernel: [   22.301872] ath9k 0000:07:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
Nov 30 10:56:25 nava-TOSHIBA-NB250 kernel: [   22.301886] ath9k 0000:07:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
Nov 30 10:56:25 nava-TOSHIBA-NB250 kernel: [   22.304070] wlan0: associate with 94:0c:6d:fe:84:60 (try 1/3)
Nov 30 10:56:25 nava-TOSHIBA-NB250 kernel: [   22.306661] wlan0: RX AssocResp from 94:0c:6d:fe:84:60 (capab=0x431 status=0 aid=1)
Nov 30 10:56:25 nava-TOSHIBA-NB250 kernel: [   22.307468] wlan0: associated
Nov 30 10:56:25 nava-TOSHIBA-NB250 kernel: [   22.307539] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): supplicant interface state: authenticating -> associating
Nov 30 10:56:25 nava-TOSHIBA-NB250 wpa_supplicant[703]: wlan0: Associated with 94:0c:6d:fe:84:60
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): supplicant interface state: associating -> associated
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Nov 30 10:56:25 nava-TOSHIBA-NB250 wpa_supplicant[703]: wlan0: WPA: Key negotiation completed with 94:0c:6d:fe:84:60 [PTK=CCMP GTK=TKIP]
Nov 30 10:56:25 nava-TOSHIBA-NB250 wpa_supplicant[703]: wlan0: CTRL-EVENT-CONNECTED - Connection to 94:0c:6d:fe:84:60 completed (auth) [id=0 id_str=]
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Priya'.
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> dhclient started with pid 934
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Beginning IP6 addrconf.
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Nov 30 10:56:25 nava-TOSHIBA-NB250 dhclient: Internet Systems Consortium DHCP Client 4.2.4
Nov 30 10:56:25 nava-TOSHIBA-NB250 dhclient: Copyright 2004-2012 Internet Systems Consortium.
Nov 30 10:56:25 nava-TOSHIBA-NB250 dhclient: All rights reserved.
Nov 30 10:56:25 nava-TOSHIBA-NB250 dhclient: For info, please visit https://www.isc.org/software/dhcp/
Nov 30 10:56:25 nava-TOSHIBA-NB250 dhclient: 
Nov 30 10:56:25 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Nov 30 10:56:25 nava-TOSHIBA-NB250 dhclient: Listening on LPF/wlan0/00:26:4d:f3:50:69
Nov 30 10:56:25 nava-TOSHIBA-NB250 dhclient: Sending on   LPF/wlan0/00:26:4d:f3:50:69
Nov 30 10:56:25 nava-TOSHIBA-NB250 dhclient: Sending on   Socket/fallback
Nov 30 10:56:25 nava-TOSHIBA-NB250 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x73e8fd32)
Nov 30 10:56:26 nava-TOSHIBA-NB250 kernel: [   23.080995] zram: module is from the staging directory, the quality is unknown, you have been warned.
Nov 30 10:56:26 nava-TOSHIBA-NB250 kernel: [   23.091611] zram: Created 2 device(s) ...
Nov 30 10:56:26 nava-TOSHIBA-NB250 kernel: [   23.214899] Adding 513572k swap on /dev/zram0.  Priority:5 extents:1 across:513572k SSFS
Nov 30 10:56:26 nava-TOSHIBA-NB250 kernel: [   23.280982] Adding 513572k swap on /dev/zram1.  Priority:5 extents:1 across:513572k SSFS
Nov 30 10:56:28 nava-TOSHIBA-NB250 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 (xid=0x73e8fd32)
Nov 30 10:56:29 nava-TOSHIBA-NB250 dhclient: DHCPREQUEST of 192.168.1.101 on wlan0 to 255.255.255.255 port 67 (xid=0x73e8fd32)
Nov 30 10:56:29 nava-TOSHIBA-NB250 dhclient: DHCPOFFER of 192.168.1.101 from 192.168.1.1
Nov 30 10:56:29 nava-TOSHIBA-NB250 dhclient: DHCPACK of 192.168.1.101 from 192.168.1.1
Nov 30 10:56:29 nava-TOSHIBA-NB250 dhclient: bound to 192.168.1.101 -- renewal in 3092 seconds.
Nov 30 10:56:29 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Nov 30 10:56:29 nava-TOSHIBA-NB250 NetworkManager[691]: <info>   address 192.168.1.101
Nov 30 10:56:29 nava-TOSHIBA-NB250 NetworkManager[691]: <info>   prefix 24 (255.255.255.0)
Nov 30 10:56:29 nava-TOSHIBA-NB250 NetworkManager[691]: <info>   gateway 192.168.1.1
Nov 30 10:56:29 nava-TOSHIBA-NB250 NetworkManager[691]: <info>   nameserver '192.168.2.1'
Nov 30 10:56:29 nava-TOSHIBA-NB250 NetworkManager[691]: <info>   nameserver '192.168.1.1'
Nov 30 10:56:29 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Nov 30 10:56:29 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Nov 30 10:56:30 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Nov 30 10:56:30 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Nov 30 10:56:30 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 30 10:56:30 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Policy set 'Priya' (wlan0) as default for IPv4 routing and DNS.
Nov 30 10:56:30 nava-TOSHIBA-NB250 NetworkManager[691]: <info> DNS: starting dnsmasq...
Nov 30 10:56:30 nava-TOSHIBA-NB250 NetworkManager[691]: <warn> dnsmasq not available on the bus, can't update servers.
Nov 30 10:56:30 nava-TOSHIBA-NB250 NetworkManager[691]: <error> [1385805390.435801] [nm-dns-dnsmasq.c:402] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Nov 30 10:56:30 nava-TOSHIBA-NB250 NetworkManager[691]: <warn> DNS: plugin dnsmasq update failed
Nov 30 10:56:30 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Writing DNS information to /sbin/resolvconf
Nov 30 10:56:33 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) successful, device activated.
Nov 30 10:56:33 nava-TOSHIBA-NB250 NetworkManager[691]: <warn> dnsmasq appeared on DBus: :1.21
Nov 30 10:56:33 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Writing DNS information to /sbin/resolvconf
Nov 30 10:56:46 nava-TOSHIBA-NB250 NetworkManager[691]: <info> (wlan0): IP6 addrconf timed out or failed.
Nov 30 10:56:46 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Nov 30 10:56:46 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Nov 30 10:56:46 nava-TOSHIBA-NB250 NetworkManager[691]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Nov 30 10:56:57 nava-TOSHIBA-NB250 kernel: [   54.310987] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Nov 30 10:56:57 nava-TOSHIBA-NB250 kernel: [   54.314223] sd 4:0:0:0: [sdb] Asking for cache data failed
Nov 30 10:56:57 nava-TOSHIBA-NB250 kernel: [   54.314237] sd 4:0:0:0: [sdb] Assuming drive cache: write through
Nov 30 10:57:49 nava-TOSHIBA-NB250 kernel: [  106.022910] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Nov 30 10:57:49 nava-TOSHIBA-NB250 kernel: [  106.026022] sd 4:0:0:0: [sdb] Asking for cache data failed
Nov 30 10:57:49 nava-TOSHIBA-NB250 kernel: [  106.026034] sd 4:0:0:0: [sdb] Assuming drive cache: write through