Pineapple rebooting especially when a client connects

[ananades]

Hey guys I'm having a frustrating time with my pineapple. It keeps rebooting especially when a client connects. I have all of the PineAP features enabled as well as urlsnarf and sslstrip. I tried using the power supply, the 6800 battery as well as the anker battery (both in 9 and 12v) as well connecting via wp5 and with the alpha (awus036neh). I tried swapping sd cards, changing the karma log from main to sd, installing infusions to both main and sd and still the same. I sometimes get it to be stable for a few hours but for the most part I keep getting reboots. Has anyone else experienced this? BTW using 2.0.3 and testing this on my own internal network with my own clients.

Thanks.

[newbi3]

Have you tried connecting it to the power coming from your wall?

[ananades]

Yes I did try the power supply as well.

I don't think I'm doing anything wrong but want to be sure. Maybe there's something faulty with mine if this is not happening to anyone else.

[newbi3]

You should try reflashing your firmware if you haven't already done so. Also you should downgrade to a previous version (1.4.1) and see if the problem persists there. If it does I would say it is safe to say you have a faulty pineapple. Also you should run "dmesg" and post the output here

[ananades]

I'm attaching the dmesg output. I already re-flashed it once and I'm about to go to 1.4.1 and see how it goes.

I tried to attach but it would not let me so I'm pasting it in. A few seconds after capturing dmesg output it rebooted again.

[ 0.000000] Linux version 3.3.8 (sebkinne@WorstationMeltdown) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #31 Thu Aug 14 23:30:25 CEST 2014

[ 0.000000] MyLoader: sysp=97d936c9, boardp=61b798de, parts=6238a85e

[ 0.000000] bootconsole [early0] enabled

[ 0.000000] CPU revision is: 00019374 (MIPS 24Kc)

[ 0.000000] SoC: Atheros AR9330 rev 1

[ 0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:25.000MHz

[ 0.000000] Determined physical RAM map:

[ 0.000000] memory: 04000000 @ 00000000 (usable)

[ 0.000000] Initrd not found or empty - disabling initrd

[ 0.000000] Zone PFN ranges:

[ 0.000000] Normal 0x00000000 -> 0x00004000

[ 0.000000] Movable zone start PFN for each node

[ 0.000000] Early memory PFN ranges

[ 0.000000] 0: 0x00000000 -> 0x00004000

[ 0.000000] On node 0 totalpages: 16384

[ 0.000000] free_area_init_node: node 0, pgdat 802d8470, node_mem_map 81000000

[ 0.000000] Normal zone: 128 pages used for memmap

[ 0.000000] Normal zone: 0 pages reserved

[ 0.000000] Normal zone: 16256 pages, LIFO batch:3

[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768

[ 0.000000] pcpu-alloc: [0] 0

[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256

[ 0.000000] Kernel command line: board=MK5 console=ttyATH0,115200 rootfstype=squashfs,jffs2 noinitrd

[ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)

[ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

[ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.

[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes

[ 0.000000] Writing ErrCtl register=00000000

[ 0.000000] Readback ErrCtl register=00000000

[ 0.000000] Memory: 61592k/65536k available (2124k kernel code, 3944k reserved, 406k data, 212k init, 0k highmem)

[ 0.000000] SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

[ 0.000000] NR_IRQS:51

[ 0.000000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)

[ 0.080000] pid_max: default: 32768 minimum: 301

[ 0.080000] Mount-cache hash table entries: 512

[ 0.090000] NET: Registered protocol family 16

[ 0.090000] gpiochip_add: registered GPIOs 0 to 29 on device: ath79

[ 0.100000] MIPS: machine is MK5 V1.0

[ 0.350000] bio: create slab <bio-0> at 0

[ 0.360000] Switching to clocksource MIPS

[ 0.360000] NET: Registered protocol family 2

[ 0.370000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

[ 0.370000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)

[ 0.370000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

[ 0.380000] TCP: Hash tables configured (established 2048 bind 2048)

[ 0.390000] TCP reno registered

[ 0.390000] UDP hash table entries: 256 (order: 0, 4096 bytes)

[ 0.400000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

[ 0.400000] NET: Registered protocol family 1

[ 0.410000] PCI: CLS 0 bytes, default 32

[ 0.430000] squashfs: version 4.0 (2009/01/31) Phillip Lougher

[ 0.430000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) © 2001-2006 Red Hat, Inc.

[ 0.440000] msgmni has been set to 120

[ 0.440000] io scheduler noop registered

[ 0.450000] io scheduler deadline registered (default)

[ 0.450000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled

[ 0.460000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART

[ 0.470000] console [ttyATH0] enabled, bootconsole disabled

[ 0.480000] m25p80 spi0.0: found w25q128, expected m25p80

[ 0.480000] m25p80 spi0.0: w25q128 (16384 Kbytes)

[ 0.490000] 5 tp-link partitions found on MTD device spi0.0

[ 0.490000] Creating 5 MTD partitions on "spi0.0":

[ 0.500000] 0x000000000000-0x000000020000 : "u-boot"

[ 0.510000] 0x000000020000-0x000000102730 : "kernel"

[ 0.510000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only

[ 0.520000] 0x000000102730-0x000000ff0000 : "rootfs"

[ 0.530000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only

[ 0.540000] mtd: partition "rootfs" set to be root filesystem

[ 0.550000] mtd: partition "rootfs_data" created automatically, ofs=C80000, len=370000

[ 0.550000] 0x000000c80000-0x000000ff0000 : "rootfs_data"

[ 0.560000] 0x000000ff0000-0x000001000000 : "art"

[ 0.570000] 0x000000020000-0x000000ff0000 : "firmware"

[ 0.590000] ag71xx_mdio: probed

[ 0.590000] eth0: Atheros AG71xx at 0xb9000000, irq 4

[ 1.150000] ag71xx ag71xx.0: eth0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]

[ 1.160000] TCP cubic registered

[ 1.160000] NET: Registered protocol family 17

[ 1.160000] Bridge firewalling registered

[ 1.170000] 8021q: 802.1Q VLAN Support v1.8

[ 1.180000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.

[ 1.180000] Freeing unused kernel memory: 212k freed

[ 3.450000] Registered led device: mk5:red:wlan1

[ 3.450000] Registered led device: mk5:blue:wlan0

[ 3.450000] Registered led device: mk5:amber:lan

[ 6.790000] JFFS2 notice: (421) jffs2_build_xattr_subsystem: complete building xattr subsystem, 3 of xdatum (1 unchecked, 2 orphan) and 25 of xref (0 dead, 10 orphan) found.

[ 7.760000] SCSI subsystem initialized

[ 8.070000] usbcore: registered new interface driver usbfs

[ 8.070000] usbcore: registered new interface driver hub

[ 8.080000] usbcore: registered new device driver usb

[ 8.630000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

[ 8.630000] ehci-platform ehci-platform: Generic Platform EHCI Controller

[ 8.640000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1

[ 8.680000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000

[ 8.700000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00

[ 8.700000] hub 1-0:1.0: USB hub found

[ 8.700000] hub 1-0:1.0: 1 port detected

[ 8.810000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver

[ 8.940000] uhci_hcd: USB Universal Host Controller Interface driver

[ 9.060000] Initializing USB Mass Storage driver...

[ 9.060000] usbcore: registered new interface driver usb-storage

[ 9.070000] USB Mass Storage support registered.

[ 9.170000] usb 1-1: new high-speed USB device number 2 using ehci-platform

[ 9.320000] hub 1-1:1.0: USB hub found

[ 9.320000] hub 1-1:1.0: 4 ports detected

[ 9.600000] usb 1-1.1: new high-speed USB device number 3 using ehci-platform

[ 9.820000] usb 1-1.2: new high-speed USB device number 4 using ehci-platform

[ 10.070000] usb 1-1.4: new high-speed USB device number 5 using ehci-platform

[ 10.200000] scsi0 : usb-storage 1-1.4:1.0

[ 11.200000] scsi 0:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0

[ 11.730000] sd 0:0:0:0: [sda] 3907584 512-byte logical blocks: (2.00 GB/1.86 GiB)

[ 11.730000] sd 0:0:0:0: [sda] Write Protect is off

[ 11.740000] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00

[ 11.740000] sd 0:0:0:0: [sda] No Caching mode page present

[ 11.740000] sd 0:0:0:0: [sda] Assuming drive cache: write through

[ 11.750000] sd 0:0:0:0: [sda] No Caching mode page present

[ 11.760000] sd 0:0:0:0: [sda] Assuming drive cache: write through

[ 11.770000] sda: sda1 sda2

[ 11.770000] sd 0:0:0:0: [sda] No Caching mode page present

[ 11.780000] sd 0:0:0:0: [sda] Assuming drive cache: write through

[ 11.780000] sd 0:0:0:0: [sda] Attached SCSI removable disk

[ 30.460000] Loading modules backported from Linux version master-2014-01-23-0-g62c147d

[ 30.460000] Backport generated by backports.git backports-20140124-0-g1256d3e

[ 30.510000] cfg80211: Calling CRDA to update world regulatory domain

[ 30.510000] cfg80211: World regulatory domain updated:

[ 30.520000] cfg80211: DFS Master region: unset

[ 30.520000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)

[ 30.530000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

[ 30.540000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

[ 30.540000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)

[ 30.550000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)

[ 30.560000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)

[ 30.570000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)

[ 32.140000] usbcore: registered new interface driver rt73usb

[ 32.200000] ath: phy0: Enable LNA combining

[ 32.200000] ath: EEPROM regdomain: 0x0

[ 32.200000] ath: EEPROM indicates default country code should be used

[ 32.200000] ath: doing EEPROM country->regdmn map search

[ 32.200000] ath: country maps to regdmn code: 0x3a

[ 32.200000] ath: Country alpha2 being used: US

[ 32.200000] ath: Regpair used: 0x3a

[ 32.210000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'

[ 32.220000] Registered led device: ath9k-phy0

[ 32.220000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2

[ 32.240000] cfg80211: Calling CRDA for country: US

[ 32.250000] cfg80211: Regulatory domain changed to country: US

[ 32.250000] cfg80211: DFS Master region: FCC

[ 32.260000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)

[ 32.270000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)

[ 32.270000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (300 mBi, 1700 mBm)

[ 32.280000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (300 mBi, 2400 mBm)

[ 32.290000] cfg80211: (5490000 KHz - 5600000 KHz @ 80000 KHz), (300 mBi, 2400 mBm)

[ 32.300000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2400 mBm)

[ 32.300000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (300 mBi, 3000 mBm)

[ 32.310000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm)

[ 32.610000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'

[ 32.610000] ieee80211 phy1: hwaddr 00:13:37:93:60:91, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2

[ 32.640000] rtl8187: Customer ID is 0x46

[ 32.640000] Registered led device: rtl8187-phy1::radio

[ 32.640000] Registered led device: rtl8187-phy1::tx

[ 32.640000] Registered led device: rtl8187-phy1::rx

[ 32.640000] rtl8187: wireless switch is on

[ 32.640000] usbcore: registered new interface driver rtl8187

[ 32.740000] Button Hotplug driver version 0.4.1

[ 32.950000] RPC: Registered named UNIX socket transport module.

[ 32.960000] RPC: Registered udp transport module.

[ 32.960000] RPC: Registered tcp transport module.

[ 32.970000] RPC: Registered tcp NFSv4.1 backchannel transport module.

[ 33.290000] PPP generic driver version 2.4.2

[ 33.430000] usb 1-1.2: reset high-speed USB device number 4 using ehci-platform

[ 33.570000] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 detected

[ 33.600000] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 0005 detected

[ 33.610000] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'

[ 33.610000] Registered led device: rt2800usb-phy2::radio

[ 33.610000] Registered led device: rt2800usb-phy2::assoc

[ 33.610000] Registered led device: rt2800usb-phy2::quality

[ 33.610000] usbcore: registered new interface driver rt2800usb

[ 33.740000] tun: Universal TUN/TAP device driver, 1.6

[ 33.750000] tun: © 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

[ 34.100000] ip_tables: © 2000-2006 Netfilter Core Team

[ 34.330000] NET: Registered protocol family 24

[ 34.470000] nf_conntrack version 0.5.0 (965 buckets, 3860 max)

[ 35.180000] xt_time: kernel timezone is -0000

[ 35.710000] usbcore: registered new interface driver ath9k_htc

[ 35.740000] usbcore: registered new interface driver cdc_acm

[ 35.750000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

[ 35.970000] usbcore: registered new interface driver usbserial

[ 35.980000] USB Serial support registered for generic

[ 35.980000] usbcore: registered new interface driver usbserial_generic

[ 35.990000] usbserial: USB Serial Driver core

[ 36.130000] usbcore: registered new interface driver asix

[ 36.210000] usbcore: registered new interface driver cdc_ether

[ 36.450000] Error: Driver 'gpio-keys-polled' is already registered, aborting...

[ 36.550000] usbcore: registered new interface driver rndis_host

[ 36.660000] sd 0:0:0:0: Attached scsi generic sg0 type 0

[ 36.690000] USB Serial support registered for GSM modem (1-port)

[ 36.690000] usbcore: registered new interface driver option

[ 36.700000] option: v0.7.2:USB Driver for GSM modems

[ 36.720000] USB Serial support registered for pl2303

[ 36.720000] usbcore: registered new interface driver pl2303

[ 36.730000] pl2303: Prolific PL2303 USB to serial adaptor driver

[ 46.250000] device eth0 entered promiscuous mode

[ 49.380000] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities

[ 49.400000] EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities

[ 49.430000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

[ 51.130000] Adding 1001324k swap on /dev/sda2. Priority:-1 extents:1 across:1001324k

[ 53.170000] device wlan0 entered promiscuous mode

[ 53.180000] br-lan: port 2(wlan0) entered forwarding state

[ 53.190000] br-lan: port 2(wlan0) entered forwarding state

[ 55.190000] br-lan: port 2(wlan0) entered forwarding state

[ 60.590000] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'

[ 60.810000] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29

[ 63.770000] wlan2: authenticate with 4a:f8:b3:39:95:39

[ 64.110000] wlan2: send auth to 4a:f8:b3:39:95:39 (try 1/3)

[ 64.120000] wlan2: authenticated

[ 64.240000] wlan2: associate with 4a:f8:b3:39:95:39 (try 1/3)

[ 64.240000] wlan2: RX AssocResp from 4a:f8:b3:39:95:39 (capab=0x411 status=0 aid=1)

[ 64.270000] wlan2: associated

[ 96.020000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.020000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.040000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.050000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.060000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.070000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.080000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.090000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.100000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.110000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.120000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.130000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.140000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.150000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.160000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.170000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.180000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.190000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.200000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.210000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.220000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.230000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.240000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.250000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.260000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.270000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.280000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.290000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.300000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.310000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.320000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.330000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.340000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.350000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.360000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.370000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.380000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.390000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.400000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.410000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.420000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.430000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.440000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.450000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.460000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.470000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.480000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.490000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.500000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.510000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.520000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.530000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.540000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.550000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.560000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.570000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.580000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.590000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.600000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.610000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.620000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.630000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.640000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.650000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.660000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.670000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.690000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.700000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.710000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.720000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 96.730000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 9 in queue 2

[ 118.790000] device mon0 entered promiscuous mode

[ 128.830000] device br-lan entered promiscuous mode

Edited August 21, 2014 by Mr-Protocol
Added spoiler tags

[ZaraByte]

I honestly think its a firmware issue some people appear to not be having problems while others are having problems. I noticed a few problems myself not sure if anyone else has the same problems because no one has posted anything like the problems i have.

[ananades]

1.4.1 has the same results. I used an android tablet to connect to the pineapple and ran speedtest and used a laptop to go to some random website and all the lights except the green and red lit up before rebooting again.

That's why I'm asking the group here. Not sure if this is a firmware issue or hardware. Maybe Seb or Darren can chime in and let us know if others have any of these issues. Kind of useless if it reboots once someone connects to it.

[L0G1C]

I was having a similar issue where my pineapple was rebooting shortly after reboot (right after I ssh'd to the unit). Turn's out it was my battery pack not really providing 2 amps of power. I'd suggest finding the highest amp 12v power adapter you can and try again.

~L0G1C

[ananades]

This is happening with the included supply which is rated at 1.5 amps at 9 volts and with the anker battery which is rated at 2 amps at 9v (and with the pineapple juice 6800). So unfortunately this is not my issue. Plus the idea is to use this with a battery and a wifi dongle. Also I can't remember where but I think I read that the MKV should work with usb 5 volts, not sure how much functionality it would have though.

[newbi3]

Yes it can work with 5 volts but you wouldn't really be able to do anything with it. I'm not sure if you have a multi meeter or not but if you do have one check to see what is coming out the of the power brick and battery. To me this sounds like a power issue either you got unlucky and got a bad battery and wall plug or you got unlucky and have a faulty pineapple which isn't receiving enough power for some reason. I am not sure if there are any programs to check power consumption that can be installed on the pineapple or not.

[ananades]

It looks like we think alike. I already tested the all the supplies. The pineapple juice 6800, the anker astro and the included power supply are all within spec. So if it is a power issue my guess is with the power circuit on the board. I'm running out of ideas and if I can't figure this out or if no-one else responds here I guess I'm going to have to contact hakshop directly.

[L0G1C]

Regardless of the output voltage of ANY of your batteries/wall adapters; if your not measuring them during load they might still be inadequate/faulty. And even then without an Oscilloscope they might intermittent issues that your are not going to see with a multimeter.

I agree that if your battery and wall adapters don't work the you have crummy luck. At the same time I know my 2 amp USB battery by PowerGen sometimes to rarely works on the pineapple (depends what I'm doing with it). Of my 2 Anker supplies one works 95% of the time and the other is about 60% of the time both with 2 amp 5V output. My stock wall wart is also sometimes an issue. However I also have external devices drawing power in some cases so is this a flaw with the stock power supply? Yes/No.. My pineapple does function with the included wall wart. Could it have been a bigger/better wall wart? YES.. And Hak5 could of charged me more too :P

Bottom line is your having issues. If you have a car and an old barrel plug of the needed size (or go to good will and find one) I'd cut it open and hook it to a 12v car battery (while the car is NOT running). A car/motorcycle battery will have 12.5v - 10v of power and can provide the needed amps for sure. I'd also recommend resetting your pineapple to stock/default functionality until this issue is resolved. It *could be* a software issue. I know if I run wifite with a -e SSID_NAME it crashes every time.

Good luck

~L0G1C

[WiFi Cowboy]

It has been my observation that the higher the voltage (up to 12v), the more stable it becomes. I agree with newbi3 that 5 volts isn't going to let you do much. I even had problems with the wall wart while streaming 1080 video with a high power ALFA. Whenever I run into a rebooting issue, I plug in to 12v to make sure it's not a lot power issue first. BTW, I found a really cool USB voltage stepper upper on eBay for like 5 or 6 bucks that you can plug into a 5v USB and get 12v USB female out the other side. I have yet to test the efficiency of this yet as I'm sure it will lose some for battery use, but it works none the less.

[Darren Kitchen]

Under normal conditions with the stock psu it should not be rebooting like that. Change variables like the power and software and that could change - but a vanilla MK5 setup will handle several clients with little load. The exact problem is difficult to diagnose here, but if we got it back in the shop I'm sure we could give it a deeper look. HakShop.com/exchange is setup to replace your pineapple with ease at no cost in this instance. We'll get you back up and running.

[ananades]

Thanks Darren, I'll do that. I was trying to make sure it wasn't a firmware issue before asking for an exchange because it seems stable at times and then out of nowhere it will reset. I thought maybe the new functionality of 2.0.3 was somehow causing it to lock up but even 1.4.1 caused the lockup reboot issues. Especially when I tried speedtest (network load??) it is almost like clockwork.

Thanks again.

[WiFi Cowboy]

My apologies Darrin, ananades. I decided to try to replicate the rebooting issue with 12v and can confirm that my problem still occurred with 12v. Sooo... I decided to investigate further into what was causing the issue and here is what I found... (All tests performed on FW version 2.0.3 with only sslstrip and WiFi manager installed, almost everything else is factory fresh)

I decided to use the wall wart for my test and put the pineapple though some serious power challenges. The wall wart seemed to not be the issue. What I did find was every time that I used wlan1 to connect to my AP and then use an external USB WiFi adaptor to rebroadcast as an AP, everything seemed OK, until...

I started streaming HD video on my laptop and after a minute or so, it would reboot. Or, if I connected wirelessly to the external USB AP with my phone, reboot.

Long story short, after testing with many different combinations of AP and client configurations (by the way, the two external USB Alfa adaptors that I used for testing where the AWUS036NHA and the AWUS036NEH) wlan1 set as client and external USB adaptor set as AP = reboot.

I could use wlan1 as client with wlan0 as AP without issue.

I could use external USB as client and wlan0 as AP without issue.

I could use an external USB as client and another external USB as AP without issue.

Only when I tried using wlan1 as client and an external USB as AP, REBOOT.

Ananades, your problem sounds (and may be) different than mine but I wanted to clarify what my problem was (and wasn't (the wall wart wasn't causing the issue)) so maybe it can help you. Has anyone else noticed this?

[ananades]

Hi WiFi Cowboy, I pretty much have dismissed a power issue being the problem. What you describe is pretty similar to what I'm doing (I tried everything, swapped a million sd cards, wifi dongles etc). The whole idea was to use the alpha as wlan2 to connect to another network to provide internet to clients since wlan1 is limited to 11mbps so my thought is that this configuration has to work.

I initially saw this with 1.4.1 (I purchased this about a month ago) but with the announcement of the new firmware I decided to wait to see if that fixes it but it didn't. At the same time I'm seeing this even though I'm connected via ethernet. I was hoping this was a firmware issue because I hate having to exchange it but it only seems like a small percentage of us are seeing this which leads me to believe this is a hardware issue of some kind (bad batch maybe?). And as a final point mine reboots when only one client (my own tablet) is connected. But your streaming video case is interesting because I'm consistently seeing it when I tried speedtest which basically is stressing the network.

So maybe that is the issue here that bandwidth is overloading something on the pineapple and it goes poof.

[fringes]

WiFi Cowboy, you clearly need more antennas.

WiFi Cowboy and ananades, you both suggest that the problem isn't power, but might be some sort of resource exhaustion. Have you tried watching the "Status" infusion to get a picture of what's going on when things start to go south? Since you both can reproduce the problem, this shouldn't be difficult.

[ananades]

No I haven't but I'll give that a go. I just re-flashed to 2.03 and wanted to leave it without any infusions just to make sure that wasn't the cause but it does reboot with the stock firmware and no infusions. I'll get 'status' and see if I can see anything there.

[ananades]

I was monitoring status while I had the pineapple running (had all pineap features enabled plus sslstrip) and once one client connected the cpu was pegging at 100% and within a few seconds it rebooted (it even happens without sslstrip). Maybe that has something to do with it. It is unusable for me. I already requested an exchange and waiting for it to be approved. I'm hoping I just have a bad one. There's just no way one connected client is causing this to fail this way. It makes no sense.

[WiFi Cowboy]

My problem seems to be something between using wlan1 connected as client and having (but not necessarily USING) an external USB NIC as an AP. If anyone is interested in more details I submitted a bug report with more info here.

fringes, I thought it might be a resource problem too so I put the little pineapple through it's paces with all of that crazy stuff plugged in (but this time not using wlan1 as a client) and it worked GREAT! Dual speed tests, streaming HD video, everything worked and it didn't re-boot as long as I wasn't using wlan1 as client and external USB running as AP at the same time.

I was just originally confused because I was testing for (and what seemed like) a power issue until I delved deeper into it. But I WAS having a power issue with 5v and re-booting originally.

Edited September 4, 2014 by WiFi Cowboy

[Darren Kitchen]

I was monitoring status while I had the pineapple running (had all pineap features enabled plus sslstrip) and once one client connected the cpu was pegging at 100% and within a few seconds it rebooted (it even happens without sslstrip). Maybe that has something to do with it. It is unusable for me. I already requested an exchange and waiting for it to be approved. I'm hoping I just have a bad one. There's just no way one connected client is causing this to fail this way. It makes no sense.

Can you tell us more about the client that connected causing the 100% CPU. Can you describe the client and what sort of network load it was pushing? Does the same happen when other clients connect or just this one? I've just come back from a job where I had over 100 clients and didn't have any issues. This is with evil portal, karma, pineap, dogma, and harverster on 2.0.4 from a new 12v pineapple juice prototype.

[ananades]

Can you tell us more about the client that connected causing the 100% CPU. Can you describe the client and what sort of network load it was pushing? Does the same happen when other clients connect or just this one? I've just come back from a job where I had over 100 clients and didn't have any issues. This is with evil portal, karma, pineap, dogma, and harverster on 2.0.4 from a new 12v pineapple juice prototype.

Sure, this happens with my HP touchpad that has cyanogen installed (ver 9 tenderloin). Once I try using speedtest it would crap out. Last night without realizing it my iPad connected to it while I was restoring from a backup after installing the GM of iOS 8 and all of a sudden I saw the slow blinking blue light that indicated to me that it rebooted. The funny thing is a few days ago I had a few connected (4-5) and it was ok. It was mostly cell phones and a kindle but I don't think much traffic was going on. The next day it started rebooting again. I believe you that it is stable for you as it seems this is only happening to a few of us. Not sure if maybe one of the components on the board is on the fritz? I'm not even doing a quarter of what this is capable of. I'm coming to the conclusion that if someone is doing something that requires some amount of bandwidth it causes the pineapple to reboot. Let me know if there's anything else you want me to try until you get this unit back.

I already got an RA# and still waiting for the shipping label but now that I know that you guys have a lot on your plate with the move I'm guessing it's going to be more that the 2 business days the email said :)

So at some point you will have this so you can debug it. I would love to know what you find and if you could post it the results that would be great.