• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 [2] 3 4
Author Topic: guruplug server plus arrived but died  (Read 21986 times)
pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #15 on: May 15, 2010, 07:00:20 PM »

I read this thread before receiving my guruplug and that got me worrried

The only "reassurance" was that no one seems to complain about it in 110v land which is where I live

SO today my plug was on all day wiht just one manual reboot. So it has been up for over 10 hours and I had
not reboot

I have a cable in eth0 going to my linksys router and I also used the wifi connection

So it looks like the problem could be a 220 issue

On the temperature side my plug gets hot. Is it normal I wouldn't know as I never had a sheevaplug. I would say that it is hot but I can
hold it in my hand and it doesn't hurt Smiley
Can you post your dmesg output? I am in Canada my guru+ also plug in to a dlink green 1008D it always die at the time when the firmware loading sequence.
Logged

Good Luck Smiley

ppmt
Full Member
***

Karma: 1
Posts: 129


View Profile
« Reply #16 on: May 15, 2010, 07:15:39 PM »

sure here it is.

Code:
sheevaplug-debian:~# dmesg
Linux version 2.6.32-00007-g56678ec (root@msi-linux-build.marvell.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33.fa1)) #1 PREEMPT Mon Feb 8 03:49:55 PST 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell Plug2L Reference Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c05881c8, node_mem_map c065f000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 130048 pages, LIFO batch:31
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 513024KB available (5144K code, 1034K data, 148K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Cache support initialised.
initial MPP regs: 01111111 11113311 33331111 33333333 00003333 00000222 00000000
  final MPP regs: 01111111 11113311 33331111 33333333 00003333 00000222 00000000
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4010, nTxLock = 32080
msgmni has been set to 1002
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 1
scsi0 : sata_mv
ata1: SATA max UDMA/133 irq 21
NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 3913 at 0x00001e920000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
ata1: SATA link down (SStatus 0 SControl F300)
UBI warning: ubi_eba_init_scan: cannot reserve enough PEBs for bad PEB handling, reserved 39, need 40
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "root"
UBI: MTD device size:            507 MiB
UBI: number of good PEBs:        4055
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 4055
UBI: number of PEBs reserved for bad PEB handling: 39
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 0
UBI: background thread "ubi_bgt0d" started, PID 454
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:01:83:90
net eth1: port 0 with MAC address 00:50:43:01:83:91
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plug2l:red:health
Registered led device: plug2l:green:health
Registered led device: plug2l:red:wmode
Registered led device: plug2l:green:wmode
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mmc0: new high speed SDIO card at address 0001
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Gating clock of unused units
before: 0x00dfc3fd
 after: 0x00cf41d9
rtc-mv rtc-mv: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
usb 1-1: new high speed USB device using orion-ehci and address 2
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   516225024 bytes (504126 KiB, 492 MiB, 4001 LEBs)
UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 148K
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high speed USB device using orion-ehci and address 3
usb 1-1.1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb 1-1.3: new high speed USB device using orion-ehci and address 4
usb 1-1.3: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas_sdio mmc0:0001:1: firmware: requesting sd8688_helper.bin
libertas: can't load helper firmware
libertas: failed to load helper firmware
libertas_sdio: probe of mmc0:0001:1 failed with error -2
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
btmrvl_sdio mmc0:0001:2: firmware: requesting sd8688_helper.bin
btmrvl_sdio_download_helper: request_firmware(helper) failed, error code = -2
btmrvl_sdio_download_fw: Failed to download helper!
btmrvl_sdio_probe: Downloading firmware failed!
scsi 1:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Attached SCSI removable disk
scsi 1:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
sd 1:0:0:1: Attached scsi generic sg1 type 0
sd 1:0:0:1: [sdb] Attached SCSI removable disk
usb-storage: device scan complete
scsi 2:0:0:0: Direct-Access     Samsung  Mighty Drive     PMAP PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 2:0:0:0: [sdc] 4026368 512-byte logical blocks: (2.06 GB/1.91 GiB)
usb-storage: device scan complete
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 23 00 00 00
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Attached SCSI removable disk
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: link up, 100 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
uap_probe: vendor=0x02DF device=0x9104 class=0 function=1
uap_sdio mmc0:0001:1: firmware: requesting mrvl/helper_sd.bin
uap_sdio mmc0:0001:1: firmware: requesting mrvl/sd8688_ap.bin
UAP FW is active
ADDRCONF(NETDEV_UP): uap0: link is not ready
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (8022 buckets, 32088 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
Bridge firewalling registered
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
eth0: no IPv6 routers present
HOST_CMD_APCMD_POWER_MODE fail=2
ADDRCONF(NETDEV_CHANGE): uap0: link becomes ready
uap0: no IPv6 routers present
HOST_CMD_APCMD_POWER_MODE fail=2
HOST_CMD_APCMD_POWER_MODE fail=2
usb 1-1.2: new full speed USB device using orion-ehci and address 5
usb 1-1.2: configuration #1 chosen from 1 choice
Linux video capture interface: v2.00
usb 1-1.2: USB disconnect, address 5
usb 1-1.2: new full speed USB device using orion-ehci and address 6
usb 1-1.2: configuration #1 chosen from 1 choice
usb 1-1.2: USB disconnect, address 6
Logged

wojo
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #17 on: May 16, 2010, 12:47:33 AM »

My guru-heater is now running for 19 hours with an usb hard drive and two ethernet connections (on 230V AC). As I already wrote I opened the case and pulled out the board a little bit. I just checked it: The heat-sink on the board is really hot, too hot in my eyes. The power supply isn't hot.

For me it looks like the heat-sink is too small and there's not enough air convection in a closed case. The power supply doesn't seem to be the source of the problem. Maybee its even a victom of the hot heat-sink.

Any other opinions or observations?

Wolfram
Logged

guidol
Full Member
***

Karma: 10
Posts: 128



View Profile
« Reply #18 on: May 16, 2010, 04:42:29 AM »

What I found out;
 - If I put a cable in eth0, it doesn't keep working all the time

My Mac is conneted via WLAN to the Guru+ and the Guru+ itself is connected via eth0 (Upper Port) to
a switch which is connected to my Fritz!Box Router.

In this combination the Guru+ is runnign now for 21Hour (around 76.000 seconds in /proc/uptime)

But has the Sheevaplug a bigger cooling system as the Guru+ ? Or is it the little bigger case with more
air in itself because there are less components?

In some cases if have seen USB-WLAN-Sticks getting real hot....so could it be possible that the heat isnt from the cpu
but from the WLAN-Chip?

So if anyone knows how to disable the WLAN (and then when its really getting no mor power) we should take a
look at the temperatur..... I have never seen a hot Bluetooth-Stick.

I attached a weather sensor for temperature on the Guru+ and it has now 37.8 degree celsius -
but feels much warmer/hot than my SheevaPlug with 27.9 degree celsius (both at around 220V/50Hz)
« Last Edit: May 17, 2010, 10:57:26 AM by guidol » Logged

Lukkie
Newbie
*

Karma: 0
Posts: 7


View Profile
« Reply #19 on: May 16, 2010, 02:27:39 PM »

I think it's good to know the following from all the users with problems:

 - Guruplug Server or Server Plus?
 - Is your plug on 110v or 220v+
 - Do you have ethernet connected? and if, only ETH0 or 1 or both?

My latest guess is that the rebooting issues are not power related, nor heat related.
I think that it has something to do with the ethernet drivers (in both u-boot and the kernel, or one of the two).

See a patch submission to u-boot back in December 2008, this is about the Marvell 88E1121 (the PHY in the Guruplug Server Plus);
http://www.mail-archive.com/u-boot@lists.denx.de/msg05529.html

I know my plug is stable when there is no ethernet connected to it. The moment I connect ethernet to it, it becomes unreliable. Unfortunately I do not have the required knowledge to "debug" this deeper, but I think I'm on to something.

So those who have issues with their Guruplug, let us know what and how you have stuff connected, and on what voltage you are running your plug. (although I do not think voltage has anything to do with it).   
Logged

JimmyLarsson
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #20 on: May 17, 2010, 09:39:07 AM »

Same thing happened to me. I got 2 units server plus. The first one worked fine at first. I was able to connect over wlan. A few minutes after connecting an ethernet connector it went dead. The upmost led (power on) went red and reboot didnt help until I connected the ethernet cable. Without ethernet connected it works great.

So I tested my second one. Same issue. The only difference is that this seems to be slightly more stabile. One ethernet-cable connected works fine until I start to do some file transfer, then it hangs. With 2 ethernet connected it wont even boot. With no cables connected it works great.

WorkED. Until now. Suddenly one of them said *POOOF* and went dead. (Does anyone know if there is a fuse that can be replaced without voiding warranty?)

230v.

Best regards
Jimmy
Logged

guidol
Full Member
***

Karma: 10
Posts: 128



View Profile
« Reply #21 on: May 17, 2010, 11:05:27 AM »

- Guruplug Server or Server Plus?
 - Is your plug on 110v or 220v+
 - Do you have ethernet connected? and if, only ETH0 or 1 or both?

Got no problem (Ok the heat of around 38 degree celsius) with a
- GuruPlug Plus
- 220V/50Hz (Voltmeter reads 216/217V)
- connected to the Ethernet at eth0 (upper port)

Did you connect the eth1 to the same switch/hub like the eth0?

Did you read something about the boot-sequence in this message:
http://plugcomputer.org/plugforum/index.php?topic=1647.msg9966#msg9966

« Last Edit: May 17, 2010, 11:07:05 AM by guidol » Logged

Lukkie
Newbie
*

Karma: 0
Posts: 7


View Profile
« Reply #22 on: May 17, 2010, 11:35:30 AM »

- connected to the Ethernet at eth0 (upper port)

What now happens when you connect a cable to eth1? And which cable do you use? The one supplied or another one?

Did you connect the eth1 to the same switch/hub like the eth0?

No, that would be silly Smiley

Did you read something about the boot-sequence in this message:
http://plugcomputer.org/plugforum/index.php?topic=1647.msg9966#msg9966

I'm going to build a kernel which does not compile the WiFi at all ... don't really need it.
Logged

guidol
Full Member
***

Karma: 10
Posts: 128



View Profile
« Reply #23 on: May 17, 2010, 01:27:11 PM »

What now happens when you connect a cable to eth1? And which cable do you use? The one supplied or another one?
I did use another ethernet-cable.... a 1:1 CAT5 yellow color

I disconnected the cable from eth0 and connected it to eth1, but I didnt get an IP-Adress from my router.
So I reconnected the cable back to eth0 and did get the DHCP-Address and voila I can Login via SSH.

PS: I now that it would be silly to connect booth ports to the same switch/hub :-)
Logged

daemondust
Newbie
*

Karma: 4
Posts: 23


View Profile
« Reply #24 on: May 17, 2010, 07:04:39 PM »

I can get eth0 or eth1 (I haven't tried both at the same time) to come up at 100 meg, but cycle link up/link down if I try to bring them up at 1 gig.
Logged

ashcrow
Newbie
*

Karma: 1
Posts: 2



View Profile WWW
« Reply #25 on: May 17, 2010, 07:10:57 PM »

I just got my Guruplug today and am having similar issues. I can connect to it via wifi as long as I don't plug any ethernet cables in. The moment I do plug in a cable the wifi stops and I get lovely a red light. Used multiple cables, plugged into different switches and routers -- same result. One jack causes it to reboot over and over. Scratch that, they both force reboots over and over!

I'm starting to believe the root password should have been "noplug4u" without the quotes.  Undecided

Also, be very careful with the network jacks if the plug has been running for more than an hour -- the metal there is very hot!!  Huh

Seriously though, I'm getting pretty frustrated. Like a lot of people I preordered because it really is a great idea, but so far I've had nothing but problems straight out of the box!
Logged

ashcrow
Newbie
*

Karma: 1
Posts: 2



View Profile WWW
« Reply #26 on: May 17, 2010, 07:16:09 PM »

I can get eth0 or eth1 (I haven't tried both at the same time) to come up at 100 meg, but cycle link up/link down if I try to bring them up at 1 gig.

You are correct! I've been using 1G switches .... pulled out the ol' 16 port 10/100M router and all of the sudden it works fine -- no more rebooting.

I threw up a quick blog post on what I did:

http://www.stevemilner.org/blog/2010/05/17/hello-guruplug-you-jerk/
« Last Edit: May 17, 2010, 08:30:04 PM by ashcrow » Logged

seacritter
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #27 on: May 17, 2010, 09:40:07 PM »

mine is running at 110v and though, a bit warm, so far so good. 

I started out with ssh and have everything upgraded and connected.  Mine is up for over 12 hours so far...
Logged

JimmyLarsson
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #28 on: May 17, 2010, 11:58:05 PM »

I can get eth0 or eth1 (I haven't tried both at the same time) to come up at 100 meg, but cycle link up/link down if I try to bring them up at 1 gig.

Is it possible to lock the speed to 100 in the plug? I am not able to change speed of the switch right now...

/Jimmy
Logged

Lukkie
Newbie
*

Karma: 0
Posts: 7


View Profile
« Reply #29 on: May 18, 2010, 12:02:21 AM »

Seriously though, I'm getting pretty frustrated. Like a lot of people I preordered because it really is a great idea, but so far I've had nothing but problems straight out of the box!

Hi Ashcrow,

You are so right. The only question now remains ... is this a hardware issue (and should the unit be RMA'd), or is it fixable in u-boot or kernel (so driver related).

My guess is its driver related. (I really hope ... Smiley)

The reasoning why I think it's driver related is that if you Google on the PHY in these plugs (88e1121) you can find some kernel fixes way way back (also see my post earlier). My guess is that the 88e1121 on the Guruplug board shares its bus with both ports, making interrupts flying in a tricky business. Hence the rebooting when you use both ports.

These are just my 2 cents, I'm not a kernel hacker nor anyway specialized in this stuff ...
Makes me wonder, are people of Marvell reading these forums? If so ... please take a look at the drivers and see if these are correctly working...
Logged

Pages: 1 [2] 3 4
Print
Jump to: