Apr 10 15:39:50 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> group handshake
Apr 10 15:39:50 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 15:39:52 pet-pc kernel: [ 2367.471940] iwlagn 0000:02:00.0: iwlagn_tx_agg_start on ra = 94:44:52:2c:90:70 tid = 0
Apr 10 16:13:11 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> group handshake
Apr 10 16:13:11 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 16:36:54 pet-pc kernel: [ 5789.750989] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:36:54 pet-pc kernel: [ 5789.750999] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:36:54 pet-pc kernel: [ 5789.756986] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:36:54 pet-pc kernel: [ 5789.756995] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:36:54 pet-pc kernel: [ 5789.870006] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:36:54 pet-pc kernel: [ 5789.870017] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:36:54 pet-pc kernel: [ 5789.876271] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:36:54 pet-pc kernel: [ 5789.876280] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:36:54 pet-pc kernel: [ 5789.890731] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:36:54 pet-pc kernel: [ 5789.890736] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:36:54 pet-pc kernel: [ 5789.899756] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:36:54 pet-pc kernel: [ 5789.899761] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:36:54 pet-pc kernel: [ 5789.916251] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:36:54 pet-pc kernel: [ 5789.916255] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:36:54 pet-pc kernel: [ 5789.922662] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:36:54 pet-pc kernel: [ 5789.922667] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:09 pet-pc kernel: [ 5804.938236] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:09 pet-pc kernel: [ 5804.938241] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:09 pet-pc kernel: [ 5804.945079] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:09 pet-pc kernel: [ 5804.945083] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:09 pet-pc kernel: [ 5804.972058] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:09 pet-pc kernel: [ 5804.972068] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:09 pet-pc kernel: [ 5804.978668] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:09 pet-pc kernel: [ 5804.978672] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:09 pet-pc kernel: [ 5804.995632] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:09 pet-pc kernel: [ 5804.995637] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:09 pet-pc kernel: [ 5805.003218] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:09 pet-pc kernel: [ 5805.003222] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:09 pet-pc kernel: [ 5805.018722] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:09 pet-pc kernel: [ 5805.018727] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.028425] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.028430] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.042887] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.042893] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.049159] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.049164] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.065902] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.065906] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.072754] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.072759] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.462462] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.462473] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.468527] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.468530] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.548622] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.548632] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.555367] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.555375] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.571999] atkbd serio0: Unknown key pressed (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.572009] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:37:10 pet-pc kernel: [ 5805.580243] atkbd serio0: Unknown key released (translated set 2, code 0x94 on isa0060/serio0).
Apr 10 16:37:10 pet-pc kernel: [ 5805.580253] atkbd serio0: Use 'setkeycodes e014 <keycode>' to make it known.
Apr 10 16:45:16 pet-pc kernel: [ 6292.004088] usb 2-2: new high speed USB device using ehci_hcd and address 3
Apr 10 16:45:17 pet-pc kernel: [ 6292.267838] NET: Registered protocol family 35
Apr 10 16:45:17 pet-pc kernel: [ 6292.293095] cdc_acm 2-2:1.1: ttyACM0: USB ACM device
Apr 10 16:45:17 pet-pc kernel: [ 6292.308738] cdc_acm 2-2:1.3: ttyACM1: USB ACM device
Apr 10 16:45:17 pet-pc kernel: [ 6292.309143] usbcore: registered new interface driver cdc_acm
Apr 10 16:45:17 pet-pc kernel: [ 6292.309146] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Apr 10 16:45:17 pet-pc kernel: [ 6292.317706] cdc_phonet: probe of 2-2:1.12 failed with error -22
Apr 10 16:45:17 pet-pc kernel: [ 6292.319571] usbcore: registered new interface driver cdc_phonet
Apr 10 16:45:17 pet-pc kernel: [ 6292.324212] usbcore: registered new interface driver cdc_ether
Apr 10 16:45:17 pet-pc modem-manager[853]: <info> (ttyACM0) opening serial port...
Apr 10 16:45:17 pet-pc kernel: [ 6292.376999] usbcore: registered new interface driver rndis_host
Apr 10 16:45:17 pet-pc kernel: [ 6292.396344] usbcore: registered new interface driver rndis_wlan
Apr 10 16:45:17 pet-pc modem-manager[853]: <info> (ttyACM1) opening serial port...
Apr 10 16:45:19 pet-pc modem-manager[853]: <info> (ttyACM0) closing serial port...
Apr 10 16:45:19 pet-pc modem-manager[853]: <info> (ttyACM0) serial port closed
Apr 10 16:45:19 pet-pc modem-manager[853]: <info> (ttyACM0) opening serial port...
Apr 10 16:45:19 pet-pc modem-manager[853]: <info> (Nokia): GSM modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2 claimed port ttyACM0
Apr 10 16:45:20 pet-pc modem-manager[853]: <info> (ttyACM0) closing serial port...
Apr 10 16:45:20 pet-pc modem-manager[853]: <info> (ttyACM0) serial port closed
Apr 10 16:45:20 pet-pc kernel: [ 6295.982779] usb 2-2: USB disconnect, address 3
Apr 10 16:45:20 pet-pc modem-manager[853]: <info> (tty/ttyACM0): released by modem /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2
Apr 10 16:45:20 pet-pc modem-manager[853]: failed to marshal parameter 1 for signal DeviceRemoved
Apr 10 16:45:20 pet-pc modem-manager[853]: <info> (ttyACM1) closing serial port...
Apr 10 16:45:20 pet-pc modem-manager[853]: <info> (ttyACM1) serial port closed
Apr 10 16:45:20 pet-pc modem-manager[853]: mm_serial_port_close: assertion `priv->open_count > 0' failed
Apr 10 16:45:21 pet-pc kernel: [ 6296.840039] usb 2-2: new high speed USB device using ehci_hcd and address 4
Apr 10 16:45:21 pet-pc kernel: [ 6297.001655] usbcore: registered new interface driver uas
Apr 10 16:45:21 pet-pc kernel: [ 6297.019948] Initializing USB Mass Storage driver...
Apr 10 16:45:21 pet-pc kernel: [ 6297.020108] scsi6 : usb-storage 2-2:1.0
Apr 10 16:45:21 pet-pc kernel: [ 6297.020228] usbcore: registered new interface driver usb-storage
Apr 10 16:45:21 pet-pc kernel: [ 6297.020230] USB Mass Storage support registered.
Apr 10 16:45:22 pet-pc kernel: [ 6298.023815] scsi 6:0:0:0: Direct-Access     Nokia    S60              1.0  PQ: 0 ANSI: 0
Apr 10 16:45:23 pet-pc kernel: [ 6298.024427] scsi 6:0:0:1: Direct-Access     Nokia    S60              1.0  PQ: 0 ANSI: 0
Apr 10 16:45:23 pet-pc kernel: [ 6298.028430] sd 6:0:0:0: Attached scsi generic sg2 type 0
Apr 10 16:45:23 pet-pc kernel: [ 6298.028942] sd 6:0:0:1: Attached scsi generic sg3 type 0
Apr 10 16:45:23 pet-pc kernel: [ 6298.034129] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Apr 10 16:45:23 pet-pc kernel: [ 6298.034747] sd 6:0:0:1: [sdc] Attached SCSI removable disk
Apr 10 16:45:27 pet-pc kernel: [ 6303.010262] sd 6:0:0:0: [sdb] 62529536 512-byte logical blocks: (32.0 GB/29.8 GiB)
Apr 10 16:45:27 pet-pc kernel: [ 6303.012176] sd 6:0:0:0: [sdb] No Caching mode page present
Apr 10 16:45:27 pet-pc kernel: [ 6303.012185] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 10 16:45:27 pet-pc kernel: [ 6303.015370] sd 6:0:0:0: [sdb] No Caching mode page present
Apr 10 16:45:27 pet-pc kernel: [ 6303.015378] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 10 16:45:28 pet-pc kernel: [ 6303.227690]  sdb: sdb1
Apr 10 16:46:32 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> group handshake
Apr 10 16:46:32 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 16:47:10 pet-pc kernel: [ 6405.412289] usb 2-2: USB disconnect, address 4
Apr 10 17:19:53 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> group handshake
Apr 10 17:19:53 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 17:53:14 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> group handshake
Apr 10 17:53:14 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 18:26:36 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> group handshake
Apr 10 18:26:36 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 18:59:57 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> group handshake
Apr 10 18:59:57 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 19:33:18 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> group handshake
Apr 10 19:33:18 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 19:47:32 pet-pc kernel: [17227.776069] CIFS VFS: Server 192.168.0.1 has not responded in 300 seconds. Reconnecting...
Apr 10 19:52:34 pet-pc kernel: [17529.124048] CIFS VFS: Server 192.168.0.1 has not responded in 300 seconds. Reconnecting...
Apr 10 19:54:50 pet-pc kernel: [17666.000086] ------------[ cut here ]------------
Apr 10 19:54:50 pet-pc kernel: [17666.000107] WARNING: at /build/buildd/linux-2.6.38/net/sched/sch_generic.c:256 dev_watchdog+0x213/0x220()
Apr 10 19:54:50 pet-pc kernel: [17666.000114] Hardware name: HP Pavilion dv6 Notebook PC       
Apr 10 19:54:50 pet-pc kernel: [17666.000119] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Apr 10 19:54:50 pet-pc kernel: [17666.000124] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat usb_storage uas rndis_wlan rndis_host cdc_ether cdc_phonet usbnet cdc_acm phonet rfcomm cryptd aes_i586 aes_generic md4 parport_pc ppdev dm_crypt snd_hda_codec_hdmi snd_hda_codec_idt arc4 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm sco iwlagn snd_seq_midi bnep snd_rawmidi snd_seq_midi_event l2cap iwlcore binfmt_misc snd_seq snd_timer snd_seq_device joydev mac80211 btusb hp_wmi uvcvideo ir_lirc_codec bluetooth lirc_dev sparse_keymap ir_sony_decoder ir_jvc_decoder jmb38x_ms ir_rc6_decoder ir_rc5_decoder snd rc_rc6_mce videodev ir_nec_decoder psmouse ene_ir memstick hp_accel serio_raw soundcore rc_core lis3lv02d nls_utf8 cifs cfg80211 snd_page_alloc input_polldev lp parport radeon ttm hid_a4tech usbhid drm_kms_helper hid drm firewire_ohci ahci video r8169 sdhci_pci firewire_core libahci sdhci crc_itu_t i2c_algo_bit
Apr 10 19:54:50 pet-pc kernel: [17666.000304] Pid: 0, comm: kworker/0:0 Tainted: G          I 2.6.38-8-generic #41-Ubuntu
Apr 10 19:54:50 pet-pc kernel: [17666.000310] Call Trace:
Apr 10 19:54:50 pet-pc kernel: [17666.000323]  [<c104f912>] ? warn_slowpath_common+0x72/0xa0
Apr 10 19:54:50 pet-pc kernel: [17666.000333]  [<c144a063>] ? dev_watchdog+0x213/0x220
Apr 10 19:54:50 pet-pc kernel: [17666.000342]  [<c144a063>] ? dev_watchdog+0x213/0x220
Apr 10 19:54:50 pet-pc kernel: [17666.000351]  [<c104f9e3>] ? warn_slowpath_fmt+0x33/0x40
Apr 10 19:54:50 pet-pc kernel: [17666.000360]  [<c144a063>] ? dev_watchdog+0x213/0x220
Apr 10 19:54:50 pet-pc kernel: [17666.000370]  [<c1069231>] ? __queue_work+0xe1/0x360
Apr 10 19:54:50 pet-pc kernel: [17666.000394]  [<f8f64990>] ? iwlagn_rx_queue_restock+0xc0/0x130 [iwlagn]
Apr 10 19:54:50 pet-pc kernel: [17666.000405]  [<c105c76b>] ? call_timer_fn+0x2b/0xe0
Apr 10 19:54:50 pet-pc kernel: [17666.000416]  [<c15107db>] ? do_IRQ+0x4b/0xc0
Apr 10 19:54:50 pet-pc kernel: [17666.000425]  [<c102d8c8>] ? default_spin_lock_flags+0x8/0x10
Apr 10 19:54:50 pet-pc kernel: [17666.000435]  [<c1449e50>] ? dev_watchdog+0x0/0x220
Apr 10 19:54:50 pet-pc kernel: [17666.000442]  [<c105daa9>] ? run_timer_softirq+0xe9/0x1e0
Apr 10 19:54:50 pet-pc kernel: [17666.000452]  [<c1449e50>] ? dev_watchdog+0x0/0x220
Apr 10 19:54:50 pet-pc kernel: [17666.000460]  [<c1056622>] ? __do_softirq+0x82/0x170
Apr 10 19:54:50 pet-pc kernel: [17666.000477]  [<c10565a0>] ? __do_softirq+0x0/0x170
Apr 10 19:54:50 pet-pc kernel: [17666.000482]  <IRQ>  [<c10567ed>] ? irq_exit+0x6d/0x80
Apr 10 19:54:50 pet-pc kernel: [17666.000497]  [<c15108ab>] ? smp_apic_timer_interrupt+0x5b/0x8a
Apr 10 19:54:50 pet-pc kernel: [17666.000507]  [<c150d305>] ? notifier_call_chain+0x45/0x60
Apr 10 19:54:50 pet-pc kernel: [17666.000515]  [<c150a0a9>] ? apic_timer_interrupt+0x31/0x38
Apr 10 19:54:50 pet-pc kernel: [17666.000524]  [<c10700d8>] ? do_cpu_nanosleep+0x38/0x1b0
Apr 10 19:54:50 pet-pc kernel: [17666.000535]  [<c12e8da4>] ? arch_local_irq_enable+0x5/0xb
Apr 10 19:54:50 pet-pc kernel: [17666.000544]  [<c12e9a8b>] ? acpi_idle_enter_bm+0x227/0x25e
Apr 10 19:54:50 pet-pc kernel: [17666.000556]  [<c14061ed>] ? cpuidle_idle_call+0x7d/0x160
Apr 10 19:54:50 pet-pc kernel: [17666.000565]  [<c10019ca>] ? cpu_idle+0x8a/0xc0
Apr 10 19:54:50 pet-pc kernel: [17666.000573]  [<c1504a7d>] ? setup_APIC_timer+0x69/0x6d
Apr 10 19:54:50 pet-pc kernel: [17666.000581]  [<c15045c1>] ? start_secondary+0xd5/0xdc
Apr 10 19:54:50 pet-pc kernel: [17666.000588] ---[ end trace a7919e7f17c0a727 ]---
Apr 10 19:54:50 pet-pc kernel: [17666.016124] r8169 0000:03:00.0: eth0: link up
Apr 10 19:56:14 pet-pc kernel: [17750.016173] r8169 0000:03:00.0: eth0: link up
Apr 10 19:57:35 pet-pc kernel: [17830.472051] CIFS VFS: Server 192.168.0.1 has not responded in 300 seconds. Reconnecting...
Apr 10 19:57:38 pet-pc kernel: [17834.016143] r8169 0000:03:00.0: eth0: link up
Apr 10 19:59:20 pet-pc kernel: [17936.016140] r8169 0000:03:00.0: eth0: link up
Apr 10 20:02:08 pet-pc kernel: [18104.016144] r8169 0000:03:00.0: eth0: link up
Apr 10 20:03:44 pet-pc kernel: [18200.016146] r8169 0000:03:00.0: eth0: link up
Apr 10 20:04:56 pet-pc kernel: [18272.016092] r8169 0000:03:00.0: eth0: link up
Apr 10 20:06:39 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> group handshake
Apr 10 20:06:39 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 20:08:32 pet-pc kernel: [18488.016095] r8169 0000:03:00.0: eth0: link up
Apr 10 20:11:20 pet-pc kernel: [18656.016181] r8169 0000:03:00.0: eth0: link up
Apr 10 20:13:02 pet-pc kernel: [18758.016096] r8169 0000:03:00.0: eth0: link up
Apr 10 20:14:26 pet-pc kernel: [18842.016153] r8169 0000:03:00.0: eth0: link up
Apr 10 20:15:14 pet-pc kernel: [18890.016141] r8169 0000:03:00.0: eth0: link up
Apr 10 20:16:08 pet-pc kernel: [18944.016129] r8169 0000:03:00.0: eth0: link up
Apr 10 20:17:56 pet-pc kernel: [19052.016131] r8169 0000:03:00.0: eth0: link up
Apr 10 20:19:32 pet-pc kernel: [19148.016139] r8169 0000:03:00.0: eth0: link up
Apr 10 20:20:26 pet-pc kernel: [19202.016134] r8169 0000:03:00.0: eth0: link up
Apr 10 20:23:32 pet-pc kernel: [19388.016151] r8169 0000:03:00.0: eth0: link up
Apr 10 20:28:56 pet-pc kernel: [19712.016142] r8169 0000:03:00.0: eth0: link up
Apr 10 20:30:02 pet-pc kernel: [19778.016153] r8169 0000:03:00.0: eth0: link up
Apr 10 20:30:56 pet-pc kernel: [19832.016138] r8169 0000:03:00.0: eth0: link up
Apr 10 20:32:20 pet-pc kernel: [19916.016155] r8169 0000:03:00.0: eth0: link up
Apr 10 20:33:50 pet-pc kernel: [20006.016146] r8169 0000:03:00.0: eth0: link up
Apr 10 20:34:56 pet-pc kernel: [20072.016145] r8169 0000:03:00.0: eth0: link up
Apr 10 20:35:44 pet-pc kernel: [20120.016141] r8169 0000:03:00.0: eth0: link up
Apr 10 20:37:14 pet-pc kernel: [20210.016121] r8169 0000:03:00.0: eth0: link up
Apr 10 20:38:50 pet-pc kernel: [20306.016135] r8169 0000:03:00.0: eth0: link up
Apr 10 20:39:50 pet-pc kernel: [20366.016145] r8169 0000:03:00.0: eth0: link up
Apr 10 20:40:44 pet-pc kernel: [20420.016148] r8169 0000:03:00.0: eth0: link up
Apr 10 20:41:38 pet-pc kernel: [20474.016144] r8169 0000:03:00.0: eth0: link up
Apr 10 20:43:08 pet-pc kernel: [20564.016185] r8169 0000:03:00.0: eth0: link up
Apr 10 20:44:26 pet-pc kernel: [20642.016147] r8169 0000:03:00.0: eth0: link up
Apr 10 20:45:50 pet-pc kernel: [20726.016158] r8169 0000:03:00.0: eth0: link up
Apr 10 20:47:32 pet-pc kernel: [20828.016158] r8169 0000:03:00.0: eth0: link up
Apr 10 20:48:44 pet-pc kernel: [20900.016137] r8169 0000:03:00.0: eth0: link up
Apr 10 20:50:02 pet-pc kernel: [20978.016150] r8169 0000:03:00.0: eth0: link up
Apr 10 20:51:44 pet-pc kernel: [21080.016188] r8169 0000:03:00.0: eth0: link up
Apr 10 20:53:02 pet-pc kernel: [21158.016153] r8169 0000:03:00.0: eth0: link up
Apr 10 20:53:56 pet-pc kernel: [21212.016137] r8169 0000:03:00.0: eth0: link up
Apr 10 20:55:20 pet-pc kernel: [21296.016187] r8169 0000:03:00.0: eth0: link up
Apr 10 20:56:20 pet-pc kernel: [21356.016152] r8169 0000:03:00.0: eth0: link up
Apr 10 20:57:26 pet-pc kernel: [21422.016153] r8169 0000:03:00.0: eth0: link up
Apr 10 20:58:56 pet-pc kernel: [21512.016079] r8169 0000:03:00.0: eth0: link up
Apr 10 21:00:14 pet-pc kernel: [21590.016173] r8169 0000:03:00.0: eth0: link up
Apr 10 21:00:38 pet-pc kernel: [21613.480560] r8169 0000:03:00.0: eth0: link down
Apr 10 21:00:38 pet-pc NetworkManager[682]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
Apr 10 21:00:38 pet-pc kernel: [21613.998697] iwlagn 0000:02:00.0: Stopping AGG while state not ON or starting
Apr 10 21:00:38 pet-pc kernel: [21614.022229] cfg80211: All devices are disconnected, going to restore regulatory settings
Apr 10 21:00:38 pet-pc kernel: [21614.022241] cfg80211: Restoring regulatory settings
Apr 10 21:00:38 pet-pc kernel: [21614.022251] cfg80211: Calling CRDA to update world regulatory domain
Apr 10 21:00:39 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  completed -> disconnected
Apr 10 21:00:39 pet-pc kernel: [21614.034047] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain 
Apr 10 21:00:39 pet-pc kernel: [21614.034063] cfg80211: World regulatory domain updated:
Apr 10 21:00:39 pet-pc kernel: [21614.034068] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 10 21:00:39 pet-pc kernel: [21614.034076] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:00:39 pet-pc kernel: [21614.034084] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:00:39 pet-pc kernel: [21614.034090] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:00:39 pet-pc kernel: [21614.034097] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:00:39 pet-pc kernel: [21614.034104] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:00:39 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> (eth0): device state change: 8 -> 2 (reason 40)
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> (eth0): deactivating device (reason: 40).
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> (eth0): canceled DHCP transaction, DHCP client pid 1269
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Policy set 'Auto Traunnetz' (wlan0) as default for IPv4 routing and DNS.
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Policy set 'Auto Traunnetz' (wlan0) as default for IPv4 routing and DNS.
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> (eth0): carrier now ON (device state 2)
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> (eth0): device state change: 2 -> 3 (reason 40)
Apr 10 21:00:43 pet-pc kernel: [21618.311272] r8169 0000:03:00.0: eth0: link up
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) starting connection 'Auto eth0'
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> (eth0): device state change: 3 -> 4 (reason 0)
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> (eth0): device state change: 4 -> 5 (reason 0)
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> (eth0): device state change: 5 -> 7 (reason 0)
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> dhclient started with pid 13329
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Apr 10 21:00:43 pet-pc dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Apr 10 21:00:43 pet-pc dhclient: Copyright 2004-2010 Internet Systems Consortium.
Apr 10 21:00:43 pet-pc dhclient: All rights reserved.
Apr 10 21:00:43 pet-pc dhclient: For info, please visit https://www.isc.org/software/dhcp/
Apr 10 21:00:43 pet-pc dhclient: 
Apr 10 21:00:43 pet-pc NetworkManager[682]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Apr 10 21:00:43 pet-pc dhclient: Listening on LPF/eth0/00:23:8b:fb:88:9b
Apr 10 21:00:43 pet-pc dhclient: Sending on   LPF/eth0/00:23:8b:fb:88:9b
Apr 10 21:00:43 pet-pc dhclient: Sending on   Socket/fallback
Apr 10 21:00:43 pet-pc dhclient: DHCPREQUEST of 192.168.0.2 on eth0 to 255.255.255.255 port 67
Apr 10 21:00:53 pet-pc dhclient: last message repeated 3 times
Apr 10 21:00:53 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 8 -> 3 (reason 11)
Apr 10 21:00:53 pet-pc NetworkManager[682]: <info> (wlan0): deactivating device (reason: 11).
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1751
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) starting connection 'Auto Traunnetz'
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  scanning -> disconnected
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0/wireless): access point 'Auto Traunnetz' has security, but secrets are required.
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0/wireless): connection 'Auto Traunnetz' has security, and secrets exist.  No new secrets needed.
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Config: added 'ssid' value 'Traunnetz'
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Config: added 'scan_ssid' value '1'
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Config: added 'psk' value '<omitted>'
Apr 10 21:00:54 pet-pc NetworkManager[682]: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 10 21:00:54 pet-pc NetworkManager[682]: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 10 21:00:54 pet-pc NetworkManager[682]: <info> Config: set interface ap_scan to 1
Apr 10 21:00:55 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Apr 10 21:00:59 pet-pc NetworkManager[682]: <info> (eth0): carrier now OFF (device state 7, deferring action for 4 seconds)
Apr 10 21:00:59 pet-pc kernel: [21634.421658] r8169 0000:03:00.0: eth0: link down
Apr 10 21:01:00 pet-pc dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Apr 10 21:01:01 pet-pc NetworkManager[682]: <info> (eth0): carrier now ON (device state 7)
Apr 10 21:01:01 pet-pc kernel: [21636.765942] r8169 0000:03:00.0: eth0: link up
Apr 10 21:01:03 pet-pc dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Apr 10 21:01:06 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  scanning -> associating
Apr 10 21:01:06 pet-pc kernel: [21641.540894] wlan0: authenticate with 94:44:52:2c:90:70 (try 1)
Apr 10 21:01:06 pet-pc kernel: [21641.543365] wlan0: authenticated
Apr 10 21:01:06 pet-pc kernel: [21641.543424] wlan0: waiting for beacon from 94:44:52:2c:90:70
Apr 10 21:01:06 pet-pc kernel: [21641.598883] wlan0: beacon received
Apr 10 21:01:06 pet-pc kernel: [21641.608055] wlan0: associate with 94:44:52:2c:90:70 (try 1)
Apr 10 21:01:06 pet-pc kernel: [21641.621534] wlan0: RX AssocResp from 94:44:52:2c:90:70 (capab=0x411 status=0 aid=1)
Apr 10 21:01:06 pet-pc kernel: [21641.621539] wlan0: associated
Apr 10 21:01:06 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  associating -> associated
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  associated -> 4-way handshake
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  4-way handshake -> group handshake
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Traunnetz'.
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 10 21:01:07 pet-pc dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Apr 10 21:01:07 pet-pc dhclient: Copyright 2004-2010 Internet Systems Consortium.
Apr 10 21:01:07 pet-pc dhclient: All rights reserved.
Apr 10 21:01:07 pet-pc dhclient: For info, please visit https://www.isc.org/software/dhcp/
Apr 10 21:01:07 pet-pc dhclient: 
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> dhclient started with pid 13398
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Apr 10 21:01:07 pet-pc dhclient: Listening on LPF/wlan0/00:22:fa:fa:da:1e
Apr 10 21:01:07 pet-pc dhclient: Sending on   LPF/wlan0/00:22:fa:fa:da:1e
Apr 10 21:01:07 pet-pc dhclient: Sending on   Socket/fallback
Apr 10 21:01:07 pet-pc dhclient: DHCPREQUEST of 192.168.0.6 on wlan0 to 255.255.255.255 port 67
Apr 10 21:01:07 pet-pc dhclient: DHCPACK of 192.168.0.6 from 192.168.0.1
Apr 10 21:01:07 pet-pc dhclient: bound to 192.168.0.6 -- renewal in 115626507 seconds.
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info>   address 192.168.0.6
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info>   prefix 24 (255.255.255.0)
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info>   gateway 192.168.0.1
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info>   nameserver '192.168.0.1'
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Scheduling stage 5
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Done scheduling stage 5
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Apr 10 21:01:07 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Apr 10 21:01:08 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Apr 10 21:01:08 pet-pc NetworkManager[682]: <info> Policy set 'Auto Traunnetz' (wlan0) as default for IPv4 routing and DNS.
Apr 10 21:01:08 pet-pc NetworkManager[682]: <info> Activation (wlan0) successful, device activated.
Apr 10 21:01:08 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Apr 10 21:01:11 pet-pc dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
Apr 10 21:01:18 pet-pc kernel: [21653.852130] CIFS VFS: Server 192.168.0.1 has not responded in 300 seconds. Reconnecting...
Apr 10 21:01:22 pet-pc kernel: [21657.120207] iwlagn 0000:02:00.0: Aggregation not enabled for tid 0 because load = 6
Apr 10 21:01:27 pet-pc kernel: [21662.940100] iwlagn 0000:02:00.0: Aggregation not enabled for tid 0 because load = 0
Apr 10 21:01:28 pet-pc dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Apr 10 21:01:28 pet-pc dhclient: DHCPOFFER of 192.168.0.2 from 192.168.0.1
Apr 10 21:01:28 pet-pc dhclient: DHCPREQUEST of 192.168.0.2 on eth0 to 255.255.255.255 port 67
Apr 10 21:01:28 pet-pc dhclient: DHCPACK of 192.168.0.2 from 192.168.0.1
Apr 10 21:01:28 pet-pc dhclient: bound to 192.168.0.2 -- renewal in 114444542 seconds.
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info> (eth0): DHCPv4 state changed preinit -> bound
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info>   address 192.168.0.2
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info>   prefix 24 (255.255.255.0)
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info>   gateway 192.168.0.1
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info>   nameserver '192.168.0.1'
Apr 10 21:01:28 pet-pc NetworkManager[682]: nm_ip4_config_add_nameserver: assertion `nameserver != s' failed
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info>   nameserver '192.168.0.1'
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info> Scheduling stage 5
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info> Done scheduling stage 5
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Apr 10 21:01:28 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Apr 10 21:01:29 pet-pc NetworkManager[682]: <info> Policy set 'Auto Traunnetz' (wlan0) as default for IPv4 routing and DNS.
Apr 10 21:01:29 pet-pc NetworkManager[682]: <info> (eth0): device state change: 7 -> 8 (reason 0)
Apr 10 21:01:29 pet-pc NetworkManager[682]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Apr 10 21:01:29 pet-pc NetworkManager[682]: <info> Activation (eth0) successful, device activated.
Apr 10 21:01:29 pet-pc NetworkManager[682]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Apr 10 21:09:38 pet-pc kernel: [22155.118384] iwlagn 0000:02:00.0: Aggregation not enabled for tid 0 because load = 2
Apr 10 21:13:11 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 8 -> 3 (reason 38)
Apr 10 21:13:11 pet-pc NetworkManager[682]: <info> (wlan0): deactivating device (reason: 38).
Apr 10 21:13:11 pet-pc NetworkManager[682]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 13398
Apr 10 21:13:11 pet-pc NetworkManager[682]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Apr 10 21:13:11 pet-pc NetworkManager[682]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Apr 10 21:13:11 pet-pc kernel: [22367.511308] wlan0: deauthenticating from 94:44:52:2c:90:70 by local choice (reason=3)
Apr 10 21:13:11 pet-pc kernel: [22367.556675] cfg80211: All devices are disconnected, going to restore regulatory settings
Apr 10 21:13:11 pet-pc kernel: [22367.556686] cfg80211: Restoring regulatory settings
Apr 10 21:13:11 pet-pc kernel: [22367.556715] cfg80211: Calling CRDA to update world regulatory domain
Apr 10 21:13:11 pet-pc kernel: [22367.566977] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain 
Apr 10 21:13:11 pet-pc kernel: [22367.566992] cfg80211: World regulatory domain updated:
Apr 10 21:13:11 pet-pc kernel: [22367.566997] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 10 21:13:11 pet-pc kernel: [22367.567005] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:13:11 pet-pc kernel: [22367.567013] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:13:11 pet-pc kernel: [22367.567020] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:13:11 pet-pc kernel: [22367.567027] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:13:11 pet-pc kernel: [22367.567034] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 10 21:13:19 pet-pc kernel: [22375.450968] ptrace of non-child pid 1970 was attempted by: opera (pid 15309)
Apr 10 21:13:20 pet-pc kernel: [22376.327845] CIFS VFS: Send error in SETFSUnixInfo = -5
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) starting connection 'Auto Traunnetz'
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0/wireless): access point 'Auto Traunnetz' has security, but secrets are required.
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0/wireless): connection 'Auto Traunnetz' has security, and secrets exist.  No new secrets needed.
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Config: added 'ssid' value 'Traunnetz'
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Config: added 'scan_ssid' value '1'
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Config: added 'psk' value '<omitted>'
Apr 10 21:13:21 pet-pc NetworkManager[682]: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 10 21:13:21 pet-pc NetworkManager[682]: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> Config: set interface ap_scan to 1
Apr 10 21:13:21 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  disconnected -> scanning
Apr 10 21:13:24 pet-pc kernel: [22380.927643] wlan0: authenticate with 94:44:52:2c:90:70 (try 1)
Apr 10 21:13:24 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  scanning -> associating
Apr 10 21:13:24 pet-pc kernel: [22380.930032] wlan0: authenticated
Apr 10 21:13:24 pet-pc kernel: [22380.930060] wlan0: associate with 94:44:52:2c:90:70 (try 1)
Apr 10 21:13:24 pet-pc kernel: [22380.933844] wlan0: RX AssocResp from 94:44:52:2c:90:70 (capab=0x411 status=0 aid=1)
Apr 10 21:13:24 pet-pc kernel: [22380.933848] wlan0: associated
Apr 10 21:13:24 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  associating -> associated
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  associated -> 4-way handshake
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  4-way handshake -> group handshake
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> (wlan0): supplicant connection state:  group handshake -> completed
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Traunnetz'.
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 10 21:13:25 pet-pc dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> dhclient started with pid 15527
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 10 21:13:25 pet-pc dhclient: Copyright 2004-2010 Internet Systems Consortium.
Apr 10 21:13:25 pet-pc dhclient: All rights reserved.
Apr 10 21:13:25 pet-pc dhclient: For info, please visit https://www.isc.org/software/dhcp/
Apr 10 21:13:25 pet-pc dhclient: 
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Apr 10 21:13:25 pet-pc dhclient: Listening on LPF/wlan0/00:22:fa:fa:da:1e
Apr 10 21:13:25 pet-pc dhclient: Sending on   LPF/wlan0/00:22:fa:fa:da:1e
Apr 10 21:13:25 pet-pc dhclient: Sending on   Socket/fallback
Apr 10 21:13:25 pet-pc dhclient: DHCPREQUEST of 192.168.0.6 on wlan0 to 255.255.255.255 port 67
Apr 10 21:13:25 pet-pc dhclient: DHCPACK of 192.168.0.6 from 192.168.0.1
Apr 10 21:13:25 pet-pc dhclient: bound to 192.168.0.6 -- renewal in 108818448 seconds.
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info>   address 192.168.0.6
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info>   prefix 24 (255.255.255.0)
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info>   gateway 192.168.0.1
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info>   nameserver '192.168.0.1'
Apr 10 21:13:25 pet-pc NetworkManager[682]: nm_ip4_config_add_nameserver: assertion `nameserver != s' failed
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info>   nameserver '192.168.0.1'
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Scheduling stage 5
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Done scheduling stage 5
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Apr 10 21:13:25 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Apr 10 21:13:26 pet-pc NetworkManager[682]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Apr 10 21:13:26 pet-pc NetworkManager[682]: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Apr 10 21:13:26 pet-pc NetworkManager[682]: <info> Activation (wlan0) successful, device activated.
Apr 10 21:13:26 pet-pc NetworkManager[682]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Apr 10 21:13:29 pet-pc kernel: [22385.641514] show_signal_msg: 15 callbacks suppressed
Apr 10 21:13:29 pet-pc kernel: [22385.641520] opera[1970]: segfault at 38 ip 086e3257 sp bfaba910 error 4 in opera[8048000+f41000]