New IT forum
27 November 2014, 02:35:33 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: GertDuino now in stock.
 
   Home   SHOP Help Search Login Register  
Pages: 1 [2] 3 4
  Print  
Author Topic: Guruplug instability  (Read 20666 times)
midtskogen
Newbie
*
Posts: 26


« Reply #15 on: 11 November 2010, 12:16:41 pm »

Thanks, Strav.

I haven't actually tried to remove the libertas module, but it's never crashed unless I've been using wifi (as a client).  That is, it doesn't crash even if libertas is loaded unless there is some wifi traffic.  So if I don't use wifi, it would be very surprising if it becomes unstable by removing libertas.
Logged
kwikrick
Newbie
*
Posts: 3


« Reply #16 on: 14 November 2010, 12:45:45 pm »


I've experienced the same problems with my Guruplug: when running in AP mode seems pretty stable, but in WLAN client mode it is definitely unstable.  It crashes completely after a couple of minutes of running idle.  No response even via serial connection.

I have the standard Guruplug Server. It runs a little warm, but I don't think the problem is heat (as is the case with the Guruplug Server PLUS).  My best guess is that the libertas wifi driver is the problem. I've not yet tried building the latest version of the driver or upgrading the firmware. I'm also still running the factory supplied kernel (i've only had it for two days). So, lots of solutions still to try...



   
Logged
midtskogen
Newbie
*
Posts: 26


« Reply #17 on: 15 November 2010, 02:33:45 pm »

It does sound like the same problem.  Please share your findings (what helps or not helps).
Logged
midtskogen
Newbie
*
Posts: 26


« Reply #18 on: 18 November 2010, 04:27:55 pm »

I had another go with Debian, which installed without problem.  The kernel is:

Linux guru 2.6.32-5-kirkwood #1 Sun Oct 31 11:19:32 UTC 2010 armv5tel GNU/Linux

I set it up as a wifi client and began copy files from it using ssh.  It went offline within a minute.  It didn't completely crash, though.  /etc/init.d/network restart on the serial port brought it back.  The syslog reveals this:

[66406.659067] libertas: problem fetching packet from firmware
[66681.543154] Unable to handle kernel paging request at virtual address 240010e7
[66681.550417] pgd = df0dc000
[66681.553169] [240010e7] *pgd=00000000
[66681.556767] Internal error: Oops: 1 [#1]
[66681.560705] last sysfs file: /sys/devices/virtual/net/lo/operstate
[66681.566912] Modules linked in: ipv6 ext2 loop btmrvl_sdio btmrvl libertas_sdio bluetooth libertas rfkill lib80211 mmc_block hmac sha1_generic mvsdio sata_mv mv643xx_eth mv_cesa libphy libata mmc_core inet_lro aes_generic ext3 jbd mbcache sd_mod crc_t10dif usb_storage scsi_mod ehci_hcd usbcore nls_base
[66681.593983] CPU: 0    Not tainted  (2.6.32-5-kirkwood #1)
[66681.599417] PC is at fget_light+0x5c/0xb8
[66681.603445] LR is at sys_read+0x18/0x6c
[66681.607299] pc : [<c00ce478>]    lr : [<c00ce220>]    psr: 00000013
[66681.607305] sp : df917f78  ip : 00000000  fp : beb2a234
[66681.618842] r10: 00000000  r9 : df916000  r8 : beb2a778
[66681.624092] r7 : 00000001  r6 : 00000000  r5 : 403b5a60  r4 : df917f8c
[66681.630650] r3 : 240010db  r2 : dfd3b0f6  r1 : df917f8c  r0 : 00000003
[66681.637208] Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[66681.644375] Control: 0005397f  Table: 1f0dc000  DAC: 00000015
[66681.650147] Process sshd (pid: 2984, stack limit = 0xdf916270)
[66681.656007] Stack: (0xdf917f78 to 0xdf918000)
[66681.660386] 7f60:                                                       2a079894 c00ce220
[66681.668604] 7f80: 00000000 2a079894 403b5af0 00000000 2a079894 403b5a60 00000000 00000003
[66681.676828] 7fa0: c0028048 c0027ea0 2a079894 403b5a60 00000003 beb2a778 00000001 00000001
[66681.685050] 7fc0: 2a079894 403b5a60 00000000 00000003 00000001 000006a8 beb2a778 beb2a234
[66681.693273] 7fe0: 00000003 beb2a228 2a04c614 403b5a7c 60000010 00000003 75fc7b6a 12b9de5d
[66681.701503] [<c00ce478>] (fget_light+0x5c/0xb8) from [<c00ce220>] (sys_read+0x18/0x6c)
[66681.709470] [<c00ce220>] (sys_read+0x18/0x6c) from [<c0027ea0>] (ret_fast_syscall+0x0/0x28)
[66681.717863] Code: e5923000 e1500003 2a000012 e5923004 (e7930100)
[66681.724256] ---[ end trace 641b79d6d30fb5ec ]---
[66750.796026] libertas: problem fetching packet from firmware
[66752.520818] libertas: problem fetching packet from firmware
[66823.146319] libertas: problem fetching packet from firmware
Logged
Strav
Newbie
*
Posts: 20


« Reply #19 on: 18 November 2010, 09:01:51 pm »

Just to let you guys know, I've posted a bunch of kernel error logs at the libertas-dev list but since a few weeks now, I haven't got any response (they're active but it seems the chipset usb8388 is getting all the attention atm).

midtskogen, if you don't mind, perhaps posting your own kern logs there will build the pressure enough for some action to take place.

Thanks!

Logged
Strav
Newbie
*
Posts: 20


« Reply #20 on: 20 November 2010, 08:56:53 am »

midtskogen: thanks Wink
Logged
kwikrick
Newbie
*
Posts: 3


« Reply #21 on: 20 November 2010, 09:55:51 am »

Although at first I though the instability problem was not heat related (since I have the standard, not the plus version), I now believe that it IS a heat problem.

I've unloaded the bluetooth related modules ('rmmod btmrvl_sdio' and uncommenting the bt related lines in the init_setup.sh script) . Now the plug will at least stay up for more than 24 hours when idle (only Wifi running in client mode).  But when I stress the CPU to 100% (stress -c 10 -t 3600) it still crashes within minutes.  Sometimes kern.log contains error messages (mostly related to the EHCI when USB devices are attached), or even unreadable garbage. Sometimes it just stops working without any errors.

Stressing the CPU will crash the plug whether it's in Wifi AP mode or client Mode or with no Wifi at all. 

I've opened it up and indeed the CPU gets frighteningly hot. What an idiot design with the heat sink IN THE MIDDLE of the device! Where's the heat supposed to go? The power wires from the PSU to the mainboard run over the heat sink and the wire insulation is actually showing signs of melting! 

Logged
midtskogen
Newbie
*
Posts: 26


« Reply #22 on: 23 November 2010, 02:09:26 pm »

I first suspected heat, but I tried to open the case.  Still it crashed.  Then I added a fan, no case.  Crash again.
Logged
judhaz
Newbie
*
Posts: 8


« Reply #23 on: 23 November 2010, 08:34:45 pm »

midtskogen: I'm planning to do an "apt-get update;apt-get upgrade". Do you think that would be safe to do now, or the current kernel known to not work on the guruplug (server plus)?
Logged
judhaz
Newbie
*
Posts: 8


« Reply #24 on: 23 November 2010, 10:05:56 pm »

Nevermind, I run kernel 2.6.32-00007-g56678ec just fine, and it is the latest lenny/stable.
Logged
Strav
Newbie
*
Posts: 20


« Reply #25 on: 24 November 2010, 05:21:05 am »

Something perhaps worth to be mentionned: when I had my guruplug on wifi client mode, I used it as a music server running mpd so it was basically hooked up on the network only to receive commands from mpd clients and this way it could remain stable for days, but as soon as I used it for heavy download traffic, it usually crashed within minutes.

I'd appreciate if someone else can confirm this: the guruplug in wifi client mode is unstable only if there's some network activity.

I think this could rule out the heat factor. Besides, I'm actually having my guruplug unrar a 4gb file, while downloading torrents and streaming music (on ethernet of course); the cpu is near 99% usage and no crash yet.

Meanwhile, I have contacted globalscale and marvell, no one seems to care. YAY
Logged
midtskogen
Newbie
*
Posts: 26


« Reply #26 on: 25 November 2010, 08:14:37 am »

judhaz: Yes, I did a reinstall a week ago, no problems (apart from the familiar wifi crashes).

Strav: I and others experience crashes in wifi client mode to a degree that it's totally unusuable.  This also happens with active cooling of the guruplug.
Logged
Strav
Newbie
*
Posts: 20


« Reply #27 on: 02 December 2010, 06:24:47 am »

He. It seems writing to GlobalScale wasn't all that fruitless. They just sent me two packages containing compiled binaries as well as the sources for the wireless drivers and firmwares. Unfortunately for me, I'm on the following kernel "Linux sheevaplug-debian 2.6.32-00007-g56678ec" and I cannot seem to find the proper headers to compile the modules (there's only the compiled bluetooth module provided and it's been compiled against 2.6.25).

Anyhow, for you who have a custom kernel and the right headers, here are the files I've been given:

http://inovo.ca/downloads/SD-WLAN-BT-UART-BT-8688-LINUX2625-SAAR-10.49.3.p70-26609.P64_B1.tar
http://inovo.ca/downloads/bt8xxx.ko

Note: if you plan to compile on the guruplug, you'll most likely have to modify or supply custom arguments to the Makefile provided for each drivers since they're written for cross-compile and most of the default settings there won't necessary match your system.

I'd be glad to hear if anything comes out of this,

Cheers!


« Last Edit: 02 December 2010, 06:47:35 am by Strav » Logged
Strav
Newbie
*
Posts: 20


« Reply #28 on: 06 December 2010, 07:56:42 pm »

Just some feedback: I cannot seem to compile the wlan sources against anything higher than kernel 2.6.32. Now I actually replaced my previous kernel with 2.6.33.7 so to test those drivers, I'll have to go back on 2.6.32 or 2.6.31 and unfortunately for the moment, I cannot seem to boot them (perhaps due to my uboot update).

I'll keep you guys posted.
« Last Edit: 07 December 2010, 02:18:59 am by Strav » Logged
sfzhi
Jr. Member
**
Posts: 54


« Reply #29 on: 08 December 2010, 06:42:33 pm »

Thanks for sharing the sources.

I don't use the plug as a wireless client, but out of curiosity I tried to compile these drivers. With kernel 2.6.33.7 it compiles without any problems. Although I haven't tried to run it yet.
Logged
Pages: 1 [2] 3 4
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!