Linux Kernel 5.4.268 Oxnas (OX820) Pogo V3 package and Debian rootfs

Hi bodhi,

Yes the system is up and running with a working network connection. It seems the issue may be with DHCPDISCOVER. I have not looked into my router settings but it might have a setting that is not getting along well with DHCP in Debian. It's really not a big deal, it just takes a little extra time during booting up. I'll look into it more and report back if I come up with anything worth passing on. I was just looking for any shortcuts you may have had.

192.168.same, sorry for any confusion. I manually replaced all the actual IP with 192.168.same to obscure the actual ip address. Probably wasn't even really necessary...

The main point I wanted to share was the issues I had updating the kernel. It took me several tries on each install. The kernel I was calling "stock" would be the one the package manager was trying to install, linux-image-4.4.38-oxnas-tld-5_5_armel.deb. It seemed when I let it install, my system would not boot, or at least I could not establish an ssh connection. I didn't want to disassemble the Pogo for a serial connection, but did end up doing so a bit later.

Is the kernel install in step 4 different than the one you offer for upgrade and if so how?

If I answered NO to the kernel installation, that resulted in not being able to create the uImage and uInitrd.

If I answered YES to the kernel install, I could not establish an ssh connection upon reboot, which I assumed was the system not booting up. I did not have a serial connection established at that time.

To get my system working, I copied and pasted the uImage and uInitrd into /boot manually, after installing your kernel. I obtained the uImage and uInitrd from the unbootable USB that I answered YES to, per above.

Because of the results I had, I wondered if it would be possible to include the uImage and uInitrd in your upgrade kernel packages.

If this doesn't add up, I'm open to performing a new USB install to help figure this out.

Now that I'm reviewing in my head as I'm writing this, it's possible that what I thought was a system not booting (YES above) because of not being able to connect via ssh, I may have not waited long enough.

I figured out after disassembly and a serial connection that it takes a long time waiting for ssh to be available for connection.

--------------------------------------------------------------
Blog: www.jeffstory.org



Edited 2 time(s). Last edit at 03/10/2017 06:19PM by JeffS.

Hi Jeff,

> ng booting up. I'll look into it more and report b
> ack if I come up with anything worth passing on. I
> was just looking for any shortcuts you may have ha
> d.

The thing that most likely will keep the DHCP stable is making sure the MAC address stays the same in Debian. In my u-boot installation, a local randomly generated MAC is used. This needs to be set to the box real MAC address. Especially if you have 2 Pogoplugs that use the same u-boot installation, then the router abosolutely needs to differentiate between the 2 boxes. So check your MAC address.

>
> 192.168.same, sorry for any confusion. I manually
> replaced all the actual IP with 192.168.same to ob
> scure the actual ip address. Probably wasn't even
> really necessary...

Yes, it is not necessary.

>
> Is the kernel install in step 4 different than the
> one you offer for upgrade and if so how?
>

Step 4 is

Quote

4. And install it with dpkg. If you encounter error with flash-kernel when running dpkg, then remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):

dpkg -i linux-image-4.4.38-oxnas-tld-5_5_armel.deb

This should be the same for all kernel versions. Every time you upgrade, this same command is applicable with a new kernel version number.


> If I answered NO to the kernel installation
> , that resulted in not being able to create the uI
> mage and uInitrd.

> If I answered YES to the kernel install, I
> could not establish an ssh connection upon reboot,
> which I assumed was the system not booting up. I d
> id not have a serial connection established at tha
> t time.

The reason you were presented with YES or NO question was what I described above. The kernel you are installing was already installed. Always say NO to the question, and then

dpkg -l | grep -i linux-image-4.4.38-oxnas-tld-5

This command will show that the kernel was already installed.

Now you are installing the same kernel on top of what is running, so you need to:

mv /lib/modules/4.4.38-oxnas-tld-5 /lib/modules/4.4.38-oxnas-tld-5.old

And run dpkg again

dpkg -i linux-image-4.4.38-oxnas-tld-5_5_armel.deb

This time you will not see the question. And the kernel linux-image-4.4.38-oxnas-tld-5 will be installed on top of the linux-image-4.4.38-oxnas-tld-5 currently running in the system.

After this, you can generated uImage and uInitrd.

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

OK and thanks for your patience bodhi,

Not being familiar with Debian package management and kernel installation is causing much confusion on my end. I really need to spend some time familiarizing myself with it and understanding the commands rather than just copy paste.

Quote
https://en.wikipedia.org/wiki/Dpkg
dpkg is used to install, remove, and provide information about .deb packages.

dpkg (Debian Package) itself is a low level tool. APT (Advanced Packaging Tool), a higher level tool, is more commonly used than dpkg as it can fetch packages from remote locations

I think things are beginning to add up now. I was thinking the command in step 4 was remotely gathering and installing any missing dependencies, files, etc. So the command in step 4 is just installing the kernel currently within /boot directory for the system to use and making package management aware of it if I'm correct?

Not sure how or why I'm getting things mucked up with this. So the terminal output I posted above was after I already had the updated kernel installed.

It's very likely the issues I was having were just me not waiting long enough for the ssh connection to be available, then assuming the system was not booting. I'll get back to this after I dedicate some time to go back through the process step by step in a new install, using a serial connection rather than an ssh.

--------------------------------------------------------------
Blog: www.jeffstory.org

Hi Jeff,

>
> I think things are beginning to add up now.
> I was thinking the command in step 4 was remotely
> gathering and installing any missing dependencies,
> files, etc. So the command in step 4 is just insta
> lling the kernel currently within /boot directory
> for the system to use and making package managemen
> t aware of it if I'm correct?

Exactly! the kernel Deb package contains everything in it. So when you run dpkg -i linux-xxx.deb, you are basically extract files into your rootfs. There are no remote gathering for more packages.

Here is a summary of what going on.

dpkg -i outputs these 4 files:

-rw-r--r-- 1 root root  149288 Feb 23 02:43 config-xxx
-rw------- 1 root root 2131409 Feb 23 03:24 System.map-xxx
-rw------- 1 root root 3302376 Feb 23 03:24 vmlinuz-xxx
-rw-r--r-- 1 root root 7711275 Feb 28 02:00 initrd.img-xxx

and populates the /lib/modules/xxx directory with the modules came with the kernel xxx.

The initrd.img-xxx file was generated based on what currently in your rootfs and the info from the linux-xxx.deb package.

> It's very likely the issues I was having were just
> me not waiting long enough for the ssh connection
> to be available, then assuming the system was not
> booting

This might have been what happened!

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

hi bodhi

I use your oxnas kernel image well.
but
oxnas kernel image usb printer not support?
I do not recognize that I want to use the Pogoplug pro as a printer server.

We will request a kernel patch for use as a print server.
please

drdos5 Wrote:
-------------------------------------------------------
> hi bodhi
>
> I use your oxnas kernel image well.
> but
> oxnas kernel image usb printer not support?
> I do not recognize that I want to use the Pogoplug
> pro as a printer server.
>
> We will request a kernel patch for use as a print
> server.
> please

drdos5,

USB printer should be already support in the kernel. What do you see in dmesg when plugging in the printer? Did the kernel detect the USB printer?

Please post output of

dmesg
lsusb

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

# dmesg
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.18.5-oxnas-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #2 SMP PREEMPT Thu Feb 12 11:17:40 PST 2015
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Pogoplug Pro
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 32768
[ 0.000000] free_area_init_node: node 0, pgdat c07d0420, node_mem_map c7efa000
[ 0.000000] Normal zone: 256 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 32768 pages, LIFO batch:7
[ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map
[ 0.000000] Start Ox820 platform
[ 0.000000] PERCPU: Embedded 9 pages/cpu @c7ee1000 s6624 r8192 d22048 u36864
[ 0.000000] pcpu-alloc: s6624 r8192 d22048 u36864 alloc=9*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 119656K/131072K available (5789K kernel code, 294K rwdata, 1704K rodata, 184K init, 236K bss, 11416K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0759918 (7495 kB)
[ 0.000000] .init : 0xc075a000 - 0xc0788000 ( 184 kB)
[ 0.000000] .data : 0xc0788000 - 0xc07d1800 ( 294 kB)
[ 0.000000] .bss : 0xc07d1800 - 0xc080cab8 ( 237 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:160
[ 0.000017] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 42949670400ns
[ 0.000192] Console: colour dummy device 80x30
[ 0.000225] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744)
[ 0.050055] pid_max: default: 32768 minimum: 301
[ 0.050227] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.050245] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.051100] Initializing cgroup subsys net_cls
[ 0.051159] CPU: Testing write buffer coherency: ok
[ 0.051563] Setting up static identity map for 0x60580b78 - 0x60580bb0
[ 0.110474] CPU1: Booted secondary processor
[ 0.170158] Brought up 2 CPUs
[ 0.170188] SMP: Total of 2 processors activated (678.29 BogoMIPS).
[ 0.171107] devtmpfs: initialized
[ 0.174080] prandom: seed boundary self test passed
[ 0.177996] prandom: 100 self tests passed
[ 0.178017] pinctrl core: initialized pinctrl subsystem
[ 0.180800] NET: Registered protocol family 16
[ 0.181314] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.185515] gpio-oxnas 44000000.gpio: at address c8848000
[ 0.185825] gpio-oxnas 44100000.gpio: at address c884a000
[ 0.186414] pinctrl-oxnas pinctrl: initialized OX820 pinctrl driver
[ 0.307893] oxnas-pcie 47c0: PCIe version/deviceID 0x82510b5
[ 0.308011] oxnas-pcie 47c0: link up
[ 0.308231] oxnas-pcie 47c0: PCI host bridge to bus 0000:00
[ 0.308254] pci_bus 0000:00: root bus resource [mem 0x48000000-0x49ffffff]
[ 0.308272] pci_bus 0000:00: root bus resource [mem 0x4a000000-0x4bdfffff pref]
[ 0.308288] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff]
[ 0.308305] pci_bus 0000:00: root bus resource [bus 00-7f]
[ 0.308359] pci 0000:00:00.0: [1814:3090] type 00 class 0x028000
[ 0.308398] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x0000ffff]
[ 0.308748] PCI: bus0: Fast back to back transfers disabled
[ 0.308830] pci 0000:00:00.0: BAR 0: assigned [mem 0x48000000-0x4800ffff]
[ 0.309212] vgaarb: loaded
[ 0.309719] SCSI subsystem initialized
[ 0.310082] libata version 3.00 loaded.
[ 0.310643] usbcore: registered new interface driver usbfs
[ 0.310778] usbcore: registered new interface driver hub
[ 0.310929] usbcore: registered new device driver usb
[ 0.311063] pps_core: LinuxPPS API ver. 1 registered
[ 0.311075] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.311121] PTP clock support registered
[ 0.312601] cfg80211: Calling CRDA to update world regulatory domain
[ 0.313057] Switched to clocksource rps_clocksource_timer
[ 0.326720] NET: Registered protocol family 2
[ 0.327680] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.327720] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[ 0.327754] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.327836] TCP: reno registered
[ 0.327864] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.327902] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.328192] NET: Registered protocol family 1
[ 0.328660] RPC: Registered named UNIX socket transport module.
[ 0.328680] RPC: Registered udp transport module.
[ 0.328691] RPC: Registered tcp transport module.
[ 0.328701] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.328747] PCI: CLS 32 bytes, default 32
[ 0.329088] Unpacking initramfs...
[ 0.534632] Freeing initrd memory: 1936K (c7c45000 - c7e29000)
[ 0.535738] futex hash table entries: 512 (order: 2, 16384 bytes)
[ 0.535818] Initialise system trusted keyring
[ 0.554524] NFS: Registering the id_resolver key type
[ 0.554577] Key type id_resolver registered
[ 0.554593] Key type id_legacy registered
[ 0.554634] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.554654] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.555555] fuse init (API version 7.23)
[ 0.556981] msgmni has been set to 237
[ 0.557488] Key type big_key registered
[ 0.561310] alg: No test for stdrng (krng)
[ 0.633157] Key type asymmetric registered
[ 0.633187] Asymmetric key parser 'x509' registered
[ 0.633328] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.633359] io scheduler noop registered
[ 0.633382] io scheduler deadline registered
[ 0.633740] io scheduler cfq registered (default)
[ 0.634273] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.635578] console [ttyS0] disabled
[ 0.635706] 44200000.uart: ttyS0 at MMIO 0x44200000 (irq = 55, base_baud = 390625) is a 16550A
[ 1.200977] console [ttyS0] enabled
[ 1.210024] loop: module loaded
[ 1.461440] scsi host0: sata_oxnas
[ 1.514900] ata1: SATA max UDMA/133 irq 50
[ 1.519260] ox820sata: reseting SATA core
[ 1.531264] nand: Could not find valid ONFI parameter page; aborting
[ 1.537628] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 1.543984] nand: Hynix NAND 128MiB 3,3V 8-bit
[ 1.548405] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[ 1.554063] Scanning device for bad blocks
[ 1.639884] 2 ofpart partitions found on MTD device 41000000.nand
[ 1.645972] Creating 2 MTD partitions on "41000000.nand":
[ 1.651368] 0x000000000000-0x000000e00000 : "boot"
[ 1.657623] 0x000000e00000-0x000008000000 : "data"
[ 1.664422] stmmaceth 40400000.ethernet: no reset control found
[ 1.670323] stmmac - user ID: 0x12, Synopsys ID: 0x35
[ 1.675374] Ring mode enabled
[ 1.678410] DMA HW capability register supported
[ 1.682926] Enhanced/Alternate descriptors
[ 1.687255] Enabled extended descriptors
[ 1.691253] RX Checksum Offload Engine supported (type 2)
[ 1.696706] TX Checksum insertion supported
[ 1.700961] Wake-Up On Lan supported
[ 1.704601] Enable RX Mitigation via HW Watchdog Timer
[ 1.731287] libphy: stmmac: probed
[ 1.734684] eth0: PHY ID 001cc914 at 0 IRQ POLL (stmmac-0:00) active
[ 1.741025] eth0: PHY ID 001cc914 at 3 IRQ POLL (stmmac-0:03)
[ 1.746880] PPP generic driver version 2.4.2
[ 1.751516] rt2800pci 0000:00:00.0: enabling device (0140 -> 0142)
[ 1.757813] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3090, rev 3213 detected
[ 1.769075] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[ 1.776386] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 1.778058] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.784604] ehci-pci: EHCI PCI platform driver
[ 1.789368] oxnas-ehci 40200100.ehci: EHCI Host Controller
[ 1.794938] oxnas-ehci 40200100.ehci: new USB bus registered, assigned bus number 1
[ 1.802744] oxnas-ehci 40200100.ehci: irq 39, io mem 0x40200100
[ 1.820582] oxnas-ehci 40200100.ehci: USB 2.0 started, EHCI 1.00
[ 1.826844] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.833664] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.840875] usb usb1: Product: EHCI Host Controller
[ 1.845731] usb usb1: Manufacturer: Linux 3.18.5-oxnas-tld-1 ehci_hcd
[ 1.852183] usb usb1: SerialNumber: 40200100.ehci
[ 1.857725] hub 1-0:1.0: USB hub found
[ 1.861575] hub 1-0:1.0: 2 ports detected
[ 1.866183] usbcore: registered new interface driver cdc_acm
[ 1.871887] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 1.879959] usbcore: registered new interface driver cdc_wdm
[ 1.885788] usbcore: registered new interface driver usb-storage
[ 1.891834] ata1: SATA link down (SStatus 0 SControl 300)
[ 1.897538] usbcore: registered new interface driver usbserial
[ 1.903464] usbcore: registered new interface driver usbserial_generic
[ 1.910031] usbserial: USB Serial support registered for generic
[ 1.916359] mousedev: PS/2 mouse device common for all mice
[ 1.921971] i2c /dev entries driver
[ 1.926594] usbcore: registered new interface driver usbhid
[ 1.932177] usbhid: USB HID core driver
[ 1.936314] TCP: cubic registered
[ 1.940733] NET: Registered protocol family 10
[ 1.946859] sit: IPv6 over IPv4 tunneling driver
[ 1.952529] NET: Registered protocol family 17
[ 1.957114] Key type dns_resolver registered
[ 1.962508] Loading compiled-in X.509 certificates
[ 1.971059] Freeing unused kernel memory: 184K (c075a000 - c0788000)
[ 2.102415] udevd[66]: starting version 175
[ 2.180761] usb 1-1: new high-speed USB device number 2 using oxnas-ehci
[ 2.342635] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 2.352176] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2.359296] usb 1-1: Product: USB2.0 Hub
[ 2.426385] hub 1-1:1.0: USB hub found
[ 2.441187] hub 1-1:1.0: 4 ports detected
[ 2.740948] usb 1-1.3: new full-speed USB device number 3 using oxnas-ehci
[ 2.853429] usb 1-1.3: New USB device found, idVendor=08bb, idProduct=2704
[ 2.860285] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.867589] usb 1-1.3: Product: USB Audio DAC
[ 2.872199] usb 1-1.3: Manufacturer: Burr-Brown from TI
[ 2.884326] input: Burr-Brown from TI USB Audio DAC as /devices/40200100.ehci/usb1/1-1/1-1.3/1-1.3:1.2/0003:08BB:2704.0001/input/input0
[ 2.898086] hid-generic 0003:08BB:2704.0001: input: USB HID v1.00 Device [Burr-Brown from TI USB Audio DAC ] on usb-40200100.ehci-1.3/input2
[ 2.990955] usb 1-1.4: new high-speed USB device number 4 using oxnas-ehci
[ 3.103552] usb 1-1.4: New USB device found, idVendor=12f7, idProduct=1d23
[ 3.110405] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.117701] usb 1-1.4: Product: Mini TD 001B
[ 3.122311] usb 1-1.4: Manufacturer: Memorex
[ 3.126645] usb 1-1.4: SerialNumber: 07751727029E
[ 3.132602] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 3.139496] scsi host1: usb-storage 1-1.4:1.0
[ 3.160903] usbcore: registered new interface driver uas
[ 4.141678] scsi 1:0:0:0: Direct-Access Memorex Mini TD 001B PMAP PQ: 0 ANSI: 0 CCS
[ 4.153917] sd 1:0:0:0: [sda] 2013184 512-byte logical blocks: (1.03 GB/983 MiB)
[ 4.162024] sd 1:0:0:0: [sda] Write Protect is off
[ 4.166809] sd 1:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 4.167393] sd 1:0:0:0: [sda] No Caching mode page found
[ 4.172743] sd 1:0:0:0: [sda] Assuming drive cache: write through
[ 4.187704] sda: sda1
[ 4.193779] sd 1:0:0:0: [sda] Attached SCSI removable disk
[ 12.769177] kjournald starting. Commit interval 5 seconds
[ 12.769236] EXT3-fs (sda1): mounted filesystem with ordered data mode
[ 14.404167] udevd[269]: starting version 175
[ 15.769221] usbcore: registered new interface driver snd-usb-audio
[ 16.984186] random: nonblocking pool is initialized
[ 17.195655] EXT3-fs (sda1): using internal journal
[ 24.506145] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
[ 24.519029] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
[ 24.801203] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 26.492940] wlan0: authenticate with 04:8d:38:9b:e0:f3
[ 26.571084] wlan0: send auth to 04:8d:38:9b:e0:f3 (try 1/3)
[ 26.578160] wlan0: authenticated
[ 26.590054] wlan0: associate with 04:8d:38:9b:e0:f3 (try 1/3)
[ 26.598771] wlan0: RX AssocResp from 04:8d:38:9b:e0:f3 (capab=0x411 status=0 aid=2)
[ 26.606566] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 26.612930] wlan0: associated

# lsusb
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0550:00f0 Fuji Xerox Co., Ltd
Bus 001 Device 003: ID 08bb:2704 Texas Instruments Japan
Bus 001 Device 004: ID 12f7:1d23 Memorex Products, Inc.



I want to use the p910nd server, but I do not have "/dev/usb/lp0", so I can not use it.

# ls /dev/usb/lp0
/dev/usb/lp0 <= not found


# cat config-4.4.48-oxnas-tld-1

# USB Device Class drivers
#
CONFIG_USB_ACM=y
# CONFIG_USB_PRINTER is not set <= Can I replace it with "y"?
CONFIG_USB_WDM=y
# CONFIG_USB_TMC is not set

drdos5 Wrote:
-------------------------------------------------------
> # dmesg
> [ 0.000000] Booting Linux on physical CPU 0x0
> [ 0.000000] Linux version 3.18.5-oxnas-tld-1 (r
> oot@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14
> ) ) #2 SMP PREEMPT Thu Feb 12 11:17:40 PST 2015
> [ 0.000000] CPU: ARMv6-compatible processor [41
> 0fb025] revision 5 (ARMv7), cr=00c5787d
> [ 0.000000] CPU: PIPT / VIPT nonaliasing data c
> ache, VIPT aliasing instruction cache
> [ 0.000000] Machine model: Pogoplug Pro
> [ 0.000000] Memory policy: Data cache writeallo
> c
> [ 0.000000] On node 0 totalpages: 32768
> [ 0.000000] free_area_init_node: node 0, pgdat
> c07d0420, node_mem_map c7efa000
> [ 0.000000] Normal zone: 256 pages used for m
> emmap
> [ 0.000000] Normal zone: 0 pages reserved
> [ 0.000000] Normal zone: 32768 pages, LIFO ba
> tch:7
> [ 0.000000] DT missing boot CPU MPIDR[23:0], fa
> ll back to default cpu_logical_map
> [ 0.000000] Start Ox820 platform
> [ 0.000000] PERCPU: Embedded 9 pages/cpu @c7ee1
> 000 s6624 r8192 d22048 u36864
> [ 0.000000] pcpu-alloc: s6624 r8192 d22048 u368
> 64 alloc=9*4096
> [ 0.000000] pcpu-alloc: [0] 0 [0] 1
> [ 0.000000] Built 1 zonelists in Zone order, mo
> bility grouping on. Total pages: 32512
> [ 0.000000] Kernel command line: console=ttyS0,
> 115200 root=/dev/sda1 rootdelay=10
> [ 0.000000] PID hash table entries: 512 (order:
> -1, 2048 bytes)
> [ 0.000000] Dentry cache hash table entries: 16
> 384 (order: 4, 65536 bytes)
> [ 0.000000] Inode-cache hash table entries: 819
> 2 (order: 3, 32768 bytes)
> [ 0.000000] Memory: 119656K/131072K available (
> 5789K kernel code, 294K rwdata, 1704K rodata, 184K
> init, 236K bss, 11416K reserved)
> [ 0.000000] Virtual kernel memory layout:
> [ 0.000000] vector : 0xffff0000 - 0xffff10
> 00 ( 4 kB)
> [ 0.000000] fixmap : 0xffc00000 - 0xffe000
> 00 (2048 kB)
> [ 0.000000] vmalloc : 0xc8800000 - 0xff0000
> 00 ( 872 MB)
> [ 0.000000] lowmem : 0xc0000000 - 0xc80000
> 00 ( 128 MB)
> [ 0.000000] modules : 0xbf000000 - 0xc00000
> 00 ( 16 MB)
> [ 0.000000] .text : 0xc0008000 - 0xc07599
> 18 (7495 kB)
> [ 0.000000] .init : 0xc075a000 - 0xc07880
> 00 ( 184 kB)
> [ 0.000000] .data : 0xc0788000 - 0xc07d18
> 00 ( 294 kB)
> [ 0.000000] .bss : 0xc07d1800 - 0xc080ca
> b8 ( 237 kB)
> [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObj
> ects=0, CPUs=2, Nodes=1
> [ 0.000000] Preemptible hierarchical RCU implem
> entation.
> [ 0.000000] NR_IRQS:160
> [ 0.000017] sched_clock: 24 bits at 390kHz, res
> olution 2560ns, wraps every 42949670400ns
> [ 0.000192] Console: colour dummy device 80x30
> [ 0.000225] Calibrating delay loop... 339.14 Bo
> goMIPS (lpj=1695744)
> [ 0.050055] pid_max: default: 32768 minimum: 30
> 1
> [ 0.050227] Mount-cache hash table entries: 102
> 4 (order: 0, 4096 bytes)
> [ 0.050245] Mountpoint-cache hash table entries
> : 1024 (order: 0, 4096 bytes)
> [ 0.051100] Initializing cgroup subsys net_cls
> [ 0.051159] CPU: Testing write buffer coherency
> : ok
> [ 0.051563] Setting up static identity map for
> 0x60580b78 - 0x60580bb0
> [ 0.110474] CPU1: Booted secondary processor
> [ 0.170158] Brought up 2 CPUs
> [ 0.170188] SMP: Total of 2 processors activate
> d (678.29 BogoMIPS).
> [ 0.171107] devtmpfs: initialized
> [ 0.174080] prandom: seed boundary self test pa
> ssed
> [ 0.177996] prandom: 100 self tests passed
> [ 0.178017] pinctrl core: initialized pinctrl s
> ubsystem
> [ 0.180800] NET: Registered protocol family 16
> [ 0.181314] DMA: preallocated 256 KiB pool for
> atomic coherent allocations
> [ 0.185515] gpio-oxnas 44000000.gpio: at addres
> s c8848000
> [ 0.185825] gpio-oxnas 44100000.gpio: at addres
> s c884a000
> [ 0.186414] pinctrl-oxnas pinctrl: initialized
> OX820 pinctrl driver
> [ 0.307893] oxnas-pcie 47c0: PCIe version/devic
> eID 0x82510b5
> [ 0.308011] oxnas-pcie 47c0: link up
> [ 0.308231] oxnas-pcie 47c0: PCI host bridge to
> bus 0000:00
> [ 0.308254] pci_bus 0000:00: root bus resource
> [mem 0x48000000-0x49ffffff]
> [ 0.308272] pci_bus 0000:00: root bus resource
> [mem 0x4a000000-0x4bdfffff pref]
> [ 0.308288] pci_bus 0000:00: root bus resource
> [io 0x0000-0xfffff]
> [ 0.308305] pci_bus 0000:00: root bus resource
> [bus 00-7f]
> [ 0.308359] pci 0000:00:00.0: [1814:3090] type
> 00 class 0x028000
> [ 0.308398] pci 0000:00:00.0: reg 0x10: [mem 0x
> 00000000-0x0000ffff]
> [ 0.308748] PCI: bus0: Fast back to back transf
> ers disabled
> [ 0.308830] pci 0000:00:00.0: BAR 0: assigned [
> mem 0x48000000-0x4800ffff]
> [ 0.309212] vgaarb: loaded
> [ 0.309719] SCSI subsystem initialized
> [ 0.310082] libata version 3.00 loaded.
> [ 0.310643] usbcore: registered new interface d
> river usbfs
> [ 0.310778] usbcore: registered new interface d
> river hub
> [ 0.310929] usbcore: registered new device driv
> er usb
> [ 0.311063] pps_core: LinuxPPS API ver. 1 regis
> tered
> [ 0.311075] pps_core: Software ver. 5.3.6 - Cop
> yright 2005-2007 Rodolfo Giometti <giometti@linux.
> it>
> [ 0.311121] PTP clock support registered
> [ 0.312601] cfg80211: Calling CRDA to update wo
> rld regulatory domain
> [ 0.313057] Switched to clocksource rps_clockso
> urce_timer
> [ 0.326720] NET: Registered protocol family 2
> [ 0.327680] TCP established hash table entries:
> 1024 (order: 0, 4096 bytes)
> [ 0.327720] TCP bind hash table entries: 1024 (
> order: 1, 8192 bytes)
> [ 0.327754] TCP: Hash tables configured (establ
> ished 1024 bind 1024)
> [ 0.327836] TCP: reno registered
> [ 0.327864] UDP hash table entries: 256 (order:
> 1, 8192 bytes)
> [ 0.327902] UDP-Lite hash table entries: 256 (o
> rder: 1, 8192 bytes)
> [ 0.328192] NET: Registered protocol family 1
> [ 0.328660] RPC: Registered named UNIX socket t
> ransport module.
> [ 0.328680] RPC: Registered udp transport modul
> e.
> [ 0.328691] RPC: Registered tcp transport modul
> e.
> [ 0.328701] RPC: Registered tcp NFSv4.1 backcha
> nnel transport module.
> [ 0.328747] PCI: CLS 32 bytes, default 32
> [ 0.329088] Unpacking initramfs...
> [ 0.534632] Freeing initrd memory: 1936K (c7c45
> 000 - c7e29000)
> [ 0.535738] futex hash table entries: 512 (orde
> r: 2, 16384 bytes)
> [ 0.535818] Initialise system trusted keyring
> [ 0.554524] NFS: Registering the id_resolver ke
> y type
> [ 0.554577] Key type id_resolver registered
> [ 0.554593] Key type id_legacy registered
> [ 0.554634] nfs4filelayout_init: NFSv4 File Lay
> out Driver Registering...
> [ 0.554654] Installing knfsd (copyright (C) 199
> 6 okir@monad.swb.de).
> [ 0.555555] fuse init (API version 7.23)
> [ 0.556981] msgmni has been set to 237
> [ 0.557488] Key type big_key registered
> [ 0.561310] alg: No test for stdrng (krng)
> [ 0.633157] Key type asymmetric registered
> [ 0.633187] Asymmetric key parser 'x509' regist
> ered
> [ 0.633328] Block layer SCSI generic (bsg) driv
> er version 0.4 loaded (major 252)
> [ 0.633359] io scheduler noop registered
> [ 0.633382] io scheduler deadline registered
> [ 0.633740] io scheduler cfq registered (defaul
> t)
> [ 0.634273] Serial: 8250/16550 driver, 1 ports,
> IRQ sharing disabled
> [ 0.635578] console [ttyS0] disabled
> [ 0.635706] 44200000.uart: ttyS0 at MMIO 0x4420
> 0000 (irq = 55, base_baud = 390625) is a 16550A
> [ 1.200977] console [ttyS0] enabled
> [ 1.210024] loop: module loaded
> [ 1.461440] scsi host0: sata_oxnas
> [ 1.514900] ata1: SATA max UDMA/133 irq 50
> [ 1.519260] ox820sata: reseting SATA core
> [ 1.531264] nand: Could not find valid ONFI par
> ameter page; aborting
> [ 1.537628] nand: device found, Manufacturer ID
> : 0xad, Chip ID: 0xf1
> [ 1.543984] nand: Hynix NAND 128MiB 3,3V 8-bit
> [ 1.548405] nand: 128MiB, SLC, page size: 2048,
> OOB size: 64
> [ 1.554063] Scanning device for bad blocks
> [ 1.639884] 2 ofpart partitions found on MTD de
> vice 41000000.nand
> [ 1.645972] Creating 2 MTD partitions on "41000
> 000.nand":
> [ 1.651368] 0x000000000000-0x000000e00000 : "bo
> ot"
> [ 1.657623] 0x000000e00000-0x000008000000 : "da
> ta"
> [ 1.664422] stmmaceth 40400000.ethernet: no res
> et control found
> [ 1.670323] stmmac - user ID: 0x12, Synopsys ID
> : 0x35
> [ 1.675374] Ring mode enabled
> [ 1.678410] DMA HW capability register support
> ed
> [ 1.682926] Enhanced/Alternate descriptors
> [ 1.687255] Enabled extended descriptors
> [ 1.691253] RX Checksum Offload Engine support
> ed (type 2)
> [ 1.696706] TX Checksum insertion supported
> [ 1.700961] Wake-Up On Lan supported
> [ 1.704601] Enable RX Mitigation via HW Watchd
> og Timer
> [ 1.731287] libphy: stmmac: probed
> [ 1.734684] eth0: PHY ID 001cc914 at 0 IRQ POLL
> (stmmac-0:00) active
> [ 1.741025] eth0: PHY ID 001cc914 at 3 IRQ POLL
> (stmmac-0:03)
> [ 1.746880] PPP generic driver version 2.4.2
> [ 1.751516] rt2800pci 0000:00:00.0: enabling de
> vice (0140 -> 0142)
> [ 1.757813] ieee80211 phy0: rt2x00_set_rt: Info
> - RT chipset 3090, rev 3213 detected
> [ 1.769075] ieee80211 phy0: rt2x00_set_rf: Info
> - RF chipset 0005 detected
> [ 1.776386] ieee80211 phy0: Selected rate contr
> ol algorithm 'minstrel_ht'
> [ 1.778058] ehci_hcd: USB 2.0 'Enhanced' Host C
> ontroller (EHCI) Driver
> [ 1.784604] ehci-pci: EHCI PCI platform driver
> [ 1.789368] oxnas-ehci 40200100.ehci: EHCI Host
> Controller
> [ 1.794938] oxnas-ehci 40200100.ehci: new USB b
> us registered, assigned bus number 1
> [ 1.802744] oxnas-ehci 40200100.ehci: irq 39, i
> o mem 0x40200100
> [ 1.820582] oxnas-ehci 40200100.ehci: USB 2.0 s
> tarted, EHCI 1.00
> [ 1.826844] usb usb1: New USB device found, idV
> endor=1d6b, idProduct=0002
> [ 1.833664] usb usb1: New USB device strings: M
> fr=3, Product=2, SerialNumber=1
> [ 1.840875] usb usb1: Product: EHCI Host Contro
> ller
> [ 1.845731] usb usb1: Manufacturer: Linux 3.18.
> 5-oxnas-tld-1 ehci_hcd
> [ 1.852183] usb usb1: SerialNumber: 40200100.eh
> ci
> [ 1.857725] hub 1-0:1.0: USB hub found
> [ 1.861575] hub 1-0:1.0: 2 ports detected
> [ 1.866183] usbcore: registered new interface d
> river cdc_acm
> [ 1.871887] cdc_acm: USB Abstract Control Model
> driver for USB modems and ISDN adapters
> [ 1.879959] usbcore: registered new interface d
> river cdc_wdm
> [ 1.885788] usbcore: registered new interface d
> river usb-storage
> [ 1.891834] ata1: SATA link down (SStatus 0 SCo
> ntrol 300)
> [ 1.897538] usbcore: registered new interface d
> river usbserial
> [ 1.903464] usbcore: registered new interface d
> river usbserial_generic
> [ 1.910031] usbserial: USB Serial support regis
> tered for generic
> [ 1.916359] mousedev: PS/2 mouse device common
> for all mice
> [ 1.921971] i2c /dev entries driver
> [ 1.926594] usbcore: registered new interface d
> river usbhid
> [ 1.932177] usbhid: USB HID core driver
> [ 1.936314] TCP: cubic registered
> [ 1.940733] NET: Registered protocol family 10
> [ 1.946859] sit: IPv6 over IPv4 tunneling drive
> r
> [ 1.952529] NET: Registered protocol family 17
> [ 1.957114] Key type dns_resolver registered
> [ 1.962508] Loading compiled-in X.509 certifica
> tes
> [ 1.971059] Freeing unused kernel memory: 184K
> (c075a000 - c0788000)
> [ 2.102415] udevd[66]: starting version 175
> [ 2.180761] usb 1-1: new high-speed USB device
> number 2 using oxnas-ehci
> [ 2.342635] usb 1-1: New USB device found, idVe
> ndor=05e3, idProduct=0608
> [ 2.352176] usb 1-1: New USB device strings: Mf
> r=0, Product=1, SerialNumber=0
> [ 2.359296] usb 1-1: Product: USB2.0 Hub
> [ 2.426385] hub 1-1:1.0: USB hub found
> [ 2.441187] hub 1-1:1.0: 4 ports detected
> [ 2.740948] usb 1-1.3: new full-speed USB devic
> e number 3 using oxnas-ehci
> [ 2.853429] usb 1-1.3: New USB device found, id
> Vendor=08bb, idProduct=2704
> [ 2.860285] usb 1-1.3: New USB device strings:
> Mfr=1, Product=2, SerialNumber=0
> [ 2.867589] usb 1-1.3: Product: USB Audio DAC
> [ 2.872199] usb 1-1.3: Manufacturer: Burr-Brown
> from TI
> [ 2.884326] input: Burr-Brown from TI
> USB Audio DAC as /devices/40200100.ehci/usb1/1-
> 1/1-1.3/1-1.3:1.2/0003:08BB:2704.0001/input/input0
> [ 2.898086] hid-generic 0003:08BB:2704.0001: in
> put: USB HID v1.00 Device [Burr-Brown from TI
> USB Audio DAC ] on usb-40200100.ehci-1.3/input2
> [ 2.990955] usb 1-1.4: new high-speed USB devic
> e number 4 using oxnas-ehci
> [ 3.103552] usb 1-1.4: New USB device found, id
> Vendor=12f7, idProduct=1d23
> [ 3.110405] usb 1-1.4: New USB device strings:
> Mfr=1, Product=2, SerialNumber=3
> [ 3.117701] usb 1-1.4: Product: Mini TD 001B
> [ 3.122311] usb 1-1.4: Manufacturer: Memorex
> [ 3.126645] usb 1-1.4: SerialNumber: 0775172702
> 9E
> [ 3.132602] usb-storage 1-1.4:1.0: USB Mass Sto
> rage device detected
> [ 3.139496] scsi host1: usb-storage 1-1.4:1.0
> [ 3.160903] usbcore: registered new interface d
> river uas
> [ 4.141678] scsi 1:0:0:0: Direct-Access Mem
> orex Mini TD 001B PMAP PQ: 0 ANSI: 0 CCS
> [ 4.153917] sd 1:0:0:0: [sda] 2013184 512-byte
> logical blocks: (1.03 GB/983 MiB)
> [ 4.162024] sd 1:0:0:0: [sda] Write Protect is
> off
> [ 4.166809] sd 1:0:0:0: [sda] Mode Sense: 23 00
> 00 00
> [ 4.167393] sd 1:0:0:0: [sda] No Caching mode p
> age found
> [ 4.172743] sd 1:0:0:0: [sda] Assuming drive ca
> che: write through
> [ 4.187704] sda: sda1
> [ 4.193779] sd 1:0:0:0: [sda] Attached SCSI rem
> ovable disk
> [ 12.769177] kjournald starting. Commit interva
> l 5 seconds
> [ 12.769236] EXT3-fs (sda1): mounted filesystem
> with ordered data mode
> [ 14.404167] udevd[269]: starting version 175
> [ 15.769221] usbcore: registered new interface d
> river snd-usb-audio
> [ 16.984186] random: nonblocking pool is initial
> ized
> [ 17.195655] EXT3-fs (sda1): using internal jour
> nal
> [ 24.506145] ieee80211 phy0: rt2x00lib_request_f
> irmware: Info - Loading firmware file 'rt2860.bin'
> [ 24.519029] ieee80211 phy0: rt2x00lib_request_f
> irmware: Info - Firmware detected - version: 0.34
> [ 24.801203] IPv6: ADDRCONF(NETDEV_UP): wlan0: l
> ink is not ready
> [ 26.492940] wlan0: authenticate with 04:8d:38:9
> b:e0:f3
> [ 26.571084] wlan0: send auth to 04:8d:38:9b:e0:
> f3 (try 1/3)
> [ 26.578160] wlan0: authenticated
> [ 26.590054] wlan0: associate with 04:8d:38:9b:e
> 0:f3 (try 1/3)
> [ 26.598771] wlan0: RX AssocResp from 04:8d:38:9
> b:e0:f3 (capab=0x411 status=0 aid=2)
> [ 26.606566] IPv6: ADDRCONF(NETDEV_CHANGE): wlan
> 0: link becomes ready
> [ 26.612930] wlan0: associated
>
> # lsusb
> Bus 001 Device 002: ID 05e3:0608 Genesys Logic, In
> c. USB-2.0 4-Port HUB
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation
> 2.0 root hub
> Bus 001 Device 005: ID 0550:00f0 Fuji Xerox Co., L
> td
> Bus 001 Device 003: ID 08bb:2704 Texas Instruments
> Japan
> Bus 001 Device 004: ID 12f7:1d23 Memorex Products,
> Inc.
>
>

Do you see you printer on this lsusb output?

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

Yes

Bus 001 Device 005: ID 0550:00f0 Fuji Xerox Co., Ltd <= "Fuji Xerox DocuPrint P205b "

drdos5,

I will add this config to my next kernel relase.

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

thank you
I will wait

Kernel linux-4.4.54-oxnas-tld-1 package was uploaded. Please see 1st post for download link.

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

mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n linux-3.12.13-oxnas-tld-5 -d /boot/vmlinuz-3.12.13-oxnas-tld-5 /boot/uImage 
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -n initramfs-3.12.13-oxnas-tld-5 -d /boot/initrd.img-3.12.13-oxnas-tld-5 /boot/uInitrd

in this two cmd,wht is the function of -n initramfs-3.12.13-oxnas-tld-5, -n linux-3.12.13-oxnas-tld-5? neither exist similar files before run nor after. I see the "man mkimage",but not be clear about this parameter. thanks.

> s-3.12.13-oxnas-tld-5, -n linux-3.12.13-oxnas-tld
> -5? neither exist similar files before run nor aft
> er. I see the "man mkimage",but not be clear about
> this parameter. thanks.

-n is the name of the image.

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

do you see the uboot run?in my test the
SPL cannot load u-boot.img from ext4.how about yours.I do this sata boot successfully. maybe I can help you.

the name? I did not find any files with this name.the man is also say so.but I don't understand what name it referred to?
by the way should you be willing to set an apt source server to up kernel by apt?

Quote

Updated 28 Mar 2017:

Fix to improve Ethernet perfornance.

Please see 1st post for workaround.

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

Hello all,

I'm using bodhi's 4.4.54 kernel on a Pogo Pro and I recently got this kernel oops in my logs:

Jun  8 00:17:13 gemstone kernel: ------------[ cut here ]------------
Jun  8 00:17:13 gemstone kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:306 dev_watchdog+0x238/0x25c()
Jun  8 00:17:13 gemstone kernel: NETDEV WATCHDOG: eth0 (oxnas-gmac): transmit queue 0 timed out
Jun  8 00:17:13 gemstone kernel: Modules linked in: xt_conntrack iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables dwmac_generic
Jun  8 00:17:13 gemstone kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.54-oxnas-tld-1 #2
Jun  8 00:17:13 gemstone kernel: Hardware name: PLXTECH NAS782X SoC (Flattened Device Tree)
Jun  8 00:17:13 gemstone kernel: [<c0010c6c>] (unwind_backtrace) from [<c000cf8c>] (show_stack+0x10/0x14)
Jun  8 00:17:13 gemstone kernel: [<c000cf8c>] (show_stack) from [<c02cf840>] (dump_stack+0x84/0xa0)
Jun  8 00:17:13 gemstone kernel: [<c02cf840>] (dump_stack) from [<c0018934>] (warn_slowpath_common+0x78/0xb4)
Jun  8 00:17:13 gemstone kernel: [<c0018934>] (warn_slowpath_common) from [<c00189a0>] (warn_slowpath_fmt+0x30/0x40)
Jun  8 00:17:13 gemstone kernel: [<c00189a0>] (warn_slowpath_fmt) from [<c04cee80>] (dev_watchdog+0x238/0x25c)
Jun  8 00:17:13 gemstone kernel: [<c04cee80>] (dev_watchdog) from [<c0064c4c>] (call_timer_fn+0x24/0x9c)
Jun  8 00:17:13 gemstone kernel: [<c0064c4c>] (call_timer_fn) from [<c0064e18>] (run_timer_softirq+0x154/0x224)
Jun  8 00:17:13 gemstone kernel: [<c0064e18>] (run_timer_softirq) from [<c001bf24>] (__do_softirq+0xfc/0x248)
Jun  8 00:17:13 gemstone kernel: [<c001bf24>] (__do_softirq) from [<c001c348>] (irq_exit+0xc4/0x110)
Jun  8 00:17:13 gemstone kernel: [<c001c348>] (irq_exit) from [<c0056aa4>] (__handle_domain_irq+0x90/0x10c)
Jun  8 00:17:13 gemstone kernel: [<c0056aa4>] (__handle_domain_irq) from [<c000942c>] (gic_handle_irq+0x38/0x7c)
Jun  8 00:17:13 gemstone kernel: [<c000942c>] (gic_handle_irq) from [<c000da20>] (__irq_svc+0x40/0x74)
Jun  8 00:17:13 gemstone kernel: Exception stack(0xc7469f88 to 0xc7469fd0)
Jun  8 00:17:13 gemstone kernel: 9f80:                   00000001 00000000 00000000 00000000 00000000 c061c62c
Jun  8 00:17:13 gemstone kernel: 9fa0: 00000000 c7469fe0 c085b2c4 c08686ac c7468000 00000000 00000000 c7469fd8
Jun  8 00:17:13 gemstone kernel: 9fc0: c000af3c c000af40 60000013 ffffffff
Jun  8 00:17:13 gemstone kernel: [<c000da20>] (__irq_svc) from [<c000af40>] (arch_cpu_idle+0x28/0x30)
Jun  8 00:17:13 gemstone kernel: [<c000af40>] (arch_cpu_idle) from [<c004d348>] (cpu_startup_entry+0x14c/0x260)
Jun  8 00:17:13 gemstone kernel: [<c004d348>] (cpu_startup_entry) from [<60009508>] (0x60009508)
Jun  8 00:17:13 gemstone kernel: ---[ end trace a45622f122d80925 ]---

It occurred when I booted my Pogo without a live network connection (that is, there was a cable in the Pogo but the switch on the other end wasn't turned on) and when the network connection went live the Pogo was unreachable (it didn't respond to ICMP packets or even ARP requests). I was forced to power cycle the box with the network connection live, after which the box was once again reachable via the network.

multiplex'd,

Thanks for reporting this. We can look at this with serial console attached, which should tell us some more info. I'll check.

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

multiplex'd,

> It occurred when I booted my Pogo without a live n
> etwork connection (that is, there was a cable in t
> he Pogo but the switch on the other end wasn't tur
> ned on) and when the network connection went live
> the Pogo was unreachable (it didn't respond to ICM
> P packets or even ARP requests). I was forced to p
> ower cycle the box with the network connection liv
> e, after which the box was once again reachable vi
> a the network.

I did a test on my Pogo Pro V3. I was able to establish the network without problem. Here is what it looks like on serial console. 51 seconds was the last line in dmesg log. At 158 seconds I plugged in the ethernet cable and the network was automatically up.

[   51.417021] NFSD: starting 90-second grace period (net c089f940)
root@PogoPro:~# [  158.610024] oxnas-gmac 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx

root@PogoPro:~#

I think your switch might be the culprit here. Is this a Gbits or Mbits switch?

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

I'm using a Gbits switch. The cable between the box and the switch was connected the entire time, except that the switch wasn't powered on to begin with. I don't know if that makes any difference; you just unplugged the cable entirely instead of having two cabled devices with one powered down.

multiplex'd Wrote:
-------------------------------------------------------
> I'm using a Gbits switch. The cable between the bo
> x and the switch was connected the entire time, ex
> cept that the switch wasn't powered on to begin wi
> th. I don't know if that makes any difference; you
> just unplugged the cable entirely instead of havin
> g two cabled devices with one powered down.

I don't think it would make any difference.

I can't easily test with switch turned off, my Dockstar is the serial console host that also connects to the switch.

The next best thing to do is you could try the same test that I did (unplug the cable) to eliminate this variable. If it does not work, then the switch has a different behavior than we would expect it to.

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

Okay, I'll try to reproduce the problem when I get the time; I'm a little busy for the next few days.

multiplex'd Wrote:
-------------------------------------------------------
> Okay, I'll try to reproduce the problem when I get
> the time; I'm a little busy for the next few days.

Unfortunately I've been unable to reproduce the issue I mentioned in my earlier post. I've tried with the cable unplugged and the cable plugged but the switch powered off, so I'm not sure what else to do now.

multiplex'd,

> sue I mentioned in my earlier post. I've tried wit
> h the cable unplugged and the cable plugged but th
> e switch powered off, so I'm not sure what else to
> do now.

I am not sure what you meant. Did the network come up OK now, in either tests?

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

bodhi,

In both the test cases the network came up correctly with no problems; I have been unable to reproduce the issue where the network does not come up correctly.

multiplex'd,

> In both the test cases the network came up correct
> ly with no problems; I have been unable to reprodu
> ce the issue where the network does not com
> e up correctly.

I see. In that case I think might be the unmanaged switch did not negotiate with the box, or something to that effect. I would wait to see if it ever happen again.

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

Hi bodhi

I am trying to upgrade my pogoplug v3 environment from the old kernel "pogoplugpro 2.6.31.6_SMP_820" + stock uboot (from your old post) to the new one described on this thread.

Since I don't have serial cable setup, I guess I would try to your latest rootfs that support stock uboot first:
Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2

However, after I followed the steps to prepared this rootfs on another usb stick and tested it. The system just wont come up and I see the front logo light keeps flashing only. Any idea what might go wrong and if there is a better/safer upgrade path I should try instead?

wwchan,

> However, after I followed the steps to prepared th
> is rootfs on another usb stick and tested it. The
> system just wont come up and I see the front logo
> light keeps flashing only. Any idea what might go
> wrong and if there is a better/safer upgrade path
> I should try instead?

Do you have a log of what you did? perhaps I can point out where the problem was. Having the new rootfs by itself is not enough to boot with stock u-boot. There must be other setup in u-boot envs to do that.

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

Hi bodhi,

First of all, thanks a lot for your reply.

I didn't keep the log of my steps done and I was following your 5 steps in "Updated 02 Nov 2014:". Can you point to the steps to make changes to the stock uboot envs?

Cheers...