Debian on NSA320s - possible?

pengu Wrote:
-------------------------------------------------------
> I'll check this ..
> following situation now:
> file transfer seems to hang sometimes but resumes
> after a while.
> In bad situations, the modification fixing the
> dhcp issue seems to help
>
>

> [Mo Sep 21 08:41:18 2015] mv643xx_eth_port
> mv643xx_eth_port.0 eth0: tx timeout
> [Mo Sep 21 08:41:18 2015] mv643xx_eth_port
> mv643xx_eth_port.0 eth0: link down
> [Mo Sep 21 08:41:18 2015] mv643xx_eth: Set the PHY
> back to auto-negotiation mode
>

I think you have network problem, check your cable, switch,...

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------

> I think you have network problem, check your
> cable, switch,...

this doesn't occur on the NSA325v2 and perhaps NSA310s
but it could caused by the same problen as mentioned earlyer (another thread, pn)
ATM I don't think so because the mentioned things (massive packet loss, reset problem of the atheros chip on my main system) doesn't occur.
This was caused by some versions of OpenWrt.
This now is something different ... but let's see

Edit
no more problems on NSA320s and none on NSA310s so far (copying a complate windows 7 installation to my other NAS)
could be something wrong wich my usb lan adapter which I have used first because of the mentioned problems with internel LAN on my main system.
After switching back to internal lan, it seems OK.
I'll try this later again on the NSA320s .. perhaps with my built kernel (4.2.1)

The network issue is gone
The power off issue remains



Edited 6 time(s). Last edit at 09/23/2015 09:26AM by pengu.

Sorry that I haven't worked on it yet but it seems the same issue as on another box I have (iomega StoreCenter ix2-dl)
Perheps is's solved here when it could be solved on this box.



pengu Wrote:
-------------------------------------------------------
> because of a second WD Red I can put two Toshiba
> 2,5 '' HDDs in this box.
> But I noticed that the power off issue still
> remains.
> I'm trying now the newest kernel + NSA320s dtb ..
> let's see...
>
> Edit
>
> same as before :-(
>

> [ 1316.847951] ------------[ cut here
> ]------------
> [ 1316.852563] WARNING: CPU: 0 PID: 3764 at
> drivers/power/reset/gpio-poweroff.c:45
> SyS_reboot+0x14c/0x1f8()
> [ 1316.861997] Modules linked in: ipv6 adt7475
> hwmon_vid evdev marvell_cesa des_generic orion_wdt
> mv_cesa gpio_keys uio_pdrv_genirq uio sg sd_mod
> uas usb_storage sata_mv libata fix
> ed scsi_mod
> [ 1316.878860] CPU: 0 PID: 3764 Comm: halt Not
> tainted 4.2.0-kirkwood-tld-1 #1
> [ 1316.885784] Hardware name: Marvell Kirkwood
> (Flattened Device Tree)
> [ 1316.892052] [<c0015ebc>] (unwind_backtrace)
> from [<c0012324>] (show_stack+0x10/0x14)
> [ 1316.899772] [<c0012324>] (show_stack) from
> [<c001f074>] (warn_slowpath_common+0x88/0xb0)
> [ 1316.907837] [<c001f074>] (warn_slowpath_common)
> from [<c001f12c>] (warn_slowpath_null+0x18/0x20)
> [ 1316.916587] [<c001f12c>] (warn_slowpath_null)
> from [<c003a404>] (SyS_reboot+0x14c/0x1f8)
> [ 1316.924648] [<c003a404>] (SyS_reboot) from
> [<c000ee80>] (ret_fast_syscall+0x0/0x38)
> [ 1316.932269] ---[ end trace 4ede80a0a9e67a41
> ]---
> [ 1348.013632] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1349.013609] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1350.013662] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1351.013594] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1352.013621] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1352.018566] usb 1-1-port1: Cannot enable. Maybe
> the USB cable is bad?
> [ 1353.023582] usb 1-1-port1: cannot disable (err
> = -110)
> [ 1354.023635] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1355.023586] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1356.023599] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1357.023558] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1358.023615] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1358.028559] usb 1-1-port1: Cannot enable. Maybe
> the USB cable is bad?
> [ 1359.033550] usb 1-1-port1: cannot disable (err
> = -110)
> [ 1360.033576] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1361.033536] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1362.033588] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1363.033525] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1364.033552] usb 1-1-port1: cannot reset (err =
> -110)
> [ 1364.038500] usb 1-1-port1: Cannot enable. Maybe
> the USB cable is bad?
> [ 1365.043511] usb 1-1-port1: cannot disable (err
> = -110)
> ...
>

>
> NSA310s dtb ... same result
>
>
> and another strange thing :-(
>
>

> [ 4758.932721] ------------[ cut here
> ]------------
> [ 4758.937356] WARNING: CPU: 0 PID: 0 at
> net/sched/sch_generic.c:303
> dev_watchdog+0x200/0x28c()
> [ 4758.945757] NETDEV WATCHDOG: eth0
> (mv643xx_eth_port): transmit queue 0 timed out
> [ 4758.953117] Modules linked in: ipv6 adt7475
> hwmon_vid raid0 md_mod evdev marvell_cesa
> des_generic mv_cesa orion_wdt uio_pdrv_genirq uio
> gpio_keys sg sd_mod uas usb_storage sata_mv libata
> fixed scsi_mod
> [ 4758.971146] CPU: 0 PID: 0 Comm: swapper Not
> tainted 4.2.0-kirkwood-tld-1 #1
> [ 4758.978070] Hardware name: Marvell Kirkwood
> (Flattened Device Tree)
> [ 4758.984338] [<c0015ebc>] (unwind_backtrace)
> from [<c0012324>] (show_stack+0x10/0x14)
> [ 4758.992058] [<c0012324>] (show_stack) from
> [<c001f074>] (warn_slowpath_common+0x88/0xb0)
> [ 4759.000122] [<c001f074>] (warn_slowpath_common)
> from [<c001f0c8>] (warn_slowpath_fmt+0x2c/0x3c)
> [ 4759.008788] [<c001f0c8>] (warn_slowpath_fmt)
> from [<c0507cec>] (dev_watchdog+0x200/0x28c)
> [ 4759.016939] [<c0507cec>] (dev_watchdog) from
> [<c006584c>] (call_timer_fn+0x8c/0x1a4)
> [ 4759.024660] [<c006584c>] (call_timer_fn) from
> [<c0065edc>] (run_timer_softirq+0x270/0x30c)
> [ 4759.032895] [<c0065edc>] (run_timer_softirq)
> from [<c00222a0>] (__do_softirq+0x134/0x2f8)
> [ 4759.041040] [<c00222a0>] (__do_softirq) from
> [<c00226cc>] (irq_exit+0x84/0xec)
> [ 4759.048245] [<c00226cc>] (irq_exit) from
> [<c0057d2c>] (__handle_domain_irq+0x98/0xcc)
> [ 4759.056049] [<c0057d2c>] (__handle_domain_irq)
> from [<c000944c>] (orion_handle_irq+0x70/0x88)
> [ 4759.064542] [<c000944c>] (orion_handle_irq)
> from [<c0012e40>] (__irq_svc+0x40/0x6c)
> [ 4759.072176] Exception stack(0xc0823f30 to
> 0xc0823f78)
> [ 4759.077210] 3f20:                              
>       0426d542 00000454 0a812795 60000013
> [ 4759.085352] 3f40: c0893e38 00000000 0a812795
> 00000454 065a5253 00000454 00000000 c08a3f38
> [ 4759.093498] 3f60: 00000003 c0823f78 c04aeb04
> c04aeb60 20000013 ffffffff
> [ 4759.100093] [<c0012e40>] (__irq_svc) from
> [<c04aeb60>] (cpuidle_enter_state+0x22c/0x33c)
> [ 4759.108163] [<c04aeb60>] (cpuidle_enter_state)
> from [<c0046b74>] (cpu_startup_entry+0x258/0x300)
> [ 4759.116923] [<c0046b74>] (cpu_startup_entry)
> from [<c07dbc20>] (start_kernel+0x358/0x3cc)
> [ 4759.125063] ---[ end trace 9dd16ffcafc32938
> ]---
> [ 4759.129668] mv643xx_eth_port mv643xx_eth_port.0
> eth0: tx timeout
> [ 4759.135743] mv643xx_eth_port mv643xx_eth_port.0
> eth0: link down
> [ 4759.155420] mv643xx_eth: Set the PHY back to
> auto-negotiation mode
> [ 4761.601582] mv643xx_eth_port mv643xx_eth_port.0
> eth0: link up, 1000 Mb/s, full duplex, flow
> control disabled
> 

Can I go from uboot 2014.07 to stock uboot 1.1.4?

cratsil1979 Wrote:
-------------------------------------------------------
> Can I go from uboot 2014.07 to stock uboot 1.1.4?

Not at the moment. But why? You meant if you can boot stock OS from the 2014 uboot?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)