2023.04 U-Boot Kirkwood - Pogo V4
Posted by bodhi
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 July 12, 2023 06:18PM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> Please run this test.
>
> - 64G Ultra or 32G Ultra rootfs attached to one of
> the rear ports.
> - 16G or 32G 2.0 Fit formatted completely (use
> fdisk to wipe the drive first) as Ext3 data drive
> attached to the other rear port.
> - 16G or 32G 2.0 Fit formatted completely (use
> fdisk to wipe the drive first) as Ext3 data drive
> attached to the top port.
>
> Power up, interrupt serial console and,
Ok, 3 drives in place.
After the first one errors, I interrupt it again, give the command again, and....no difference.
Keep in mind that it does this even with 3 formatted drives and no rootfs - obviously it wouldn't boot, but it errors the same when checking the USB nonetheless.
Here's something very interesting - when the 3.2 is in the top rear, and a 2.0 is in the bottom rear, it works and shows the following:
But move the 2.0 from a rear port to the top port next to the sata port, and I get the USB error:
Anything else I can provide? I did find a trove of older thumbdrives of 8G or less by various manufacturers if you'd like for me to try those too (initial tests show failures as well, but I wasn't scientific about it).
Edited 2 time(s). Last edit at 07/12/2023 06:24PM by dhargens.
-------------------------------------------------------
> Please run this test.
>
> - 64G Ultra or 32G Ultra rootfs attached to one of
> the rear ports.
> - 16G or 32G 2.0 Fit formatted completely (use
> fdisk to wipe the drive first) as Ext3 data drive
> attached to the other rear port.
> - 16G or 32G 2.0 Fit formatted completely (use
> fdisk to wipe the drive first) as Ext3 data drive
> attached to the top port.
>
> Power up, interrupt serial console and,
> usb start > usb storage > usb tree> And post the entire serial console log here.
Ok, 3 drives in place.
After the first one errors, I interrupt it again, give the command again, and....no difference.
Keep in mind that it does this even with 3 formatted drives and no rootfs - obviously it wouldn't boot, but it errors the same when checking the USB nonetheless.
U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 Model: Cloud Engines PogoPlug Series 4 DRAM: 128 MiB Core: 20 devices, 16 uclasses, devicetree: separate NAND: 128 MiB MMC: mvsdio@90000: 0 Loading Environment from NAND... OK Resetting console stdin/stdout/stderr to serial... In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000 Hit any key to stop autoboot: 0 Pogo_V4> usb start starting USB... Bus ehci@50000: USB EHCI 1.00 Bus xhci_pci: Register 400081f NbrPorts 4 Starting the controller USB XHCI 1.00 scanning bus ehci@50000 for devices... 2 USB Device(s) found scanning bus xhci_pci for devices... XHCI timeout on event type 33... cannot recover. BUG at drivers/usb/host/xhci-ring.c:496/xhci_wait_for_event()! BUG! resetting ... U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 Model: Cloud Engines PogoPlug Series 4 DRAM: 128 MiB Core: 20 devices, 16 uclasses, devicetree: separate NAND: 128 MiB MMC: mvsdio@90000: 0 Loading Environment from NAND... OK Resetting console stdin/stdout/stderr to serial... In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000 Hit any key to stop autoboot: 0 Pogo_V4> usb start starting USB... Bus ehci@50000: USB EHCI 1.00 Bus xhci_pci: Register 400081f NbrPorts 4 Starting the controller USB XHCI 1.00 scanning bus ehci@50000 for devices... 2 USB Device(s) found scanning bus xhci_pci for devices... XHCI timeout on event type 33... cannot recover. BUG at drivers/usb/host/xhci-ring.c:496/xhci_wait_for_event()! BUG! resetting ... U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 Model: Cloud Engines PogoPlug Series 4 DRAM: 128 MiB Core: 20 devices, 16 uclasses, devicetree: separate NAND: 128 MiB MMC: mvsdio@90000: 0 Loading Environment from NAND... OK Resetting console stdin/stdout/stderr to serial... In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000 Hit any key to stop autoboot: 0 Pogo_V4>
Here's something very interesting - when the 3.2 is in the top rear, and a 2.0 is in the bottom rear, it works and shows the following:
U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700)
Pogoplug V4
SoC: Kirkwood 88F6192_A1
Model: Cloud Engines PogoPlug Series 4
DRAM: 128 MiB
Core: 20 devices, 16 uclasses, devicetree: separate
NAND: 128 MiB
MMC: mvsdio@90000: 0
Loading Environment from NAND... OK
Resetting console stdin/stdout/stderr to serial...
In: serial
Out: serial
Err: serial
pcie0.0: Link up
Net: eth0: ethernet-controller@72000
Hit any key to stop autoboot: 0
Pogo_V4> usb start
starting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 3 USB Device(s) found
scanning usb for storage devices... 2 Storage Device(s) found
Pogo_V4> usb storage
Device 0: Vendor: SanDisk' Rev: 1.00 Prod: Cruzer Fit
Type: Removable Hard Disk
Capacity: 14664.0 MB = 14.3 GB (30031872 x 512)
Device 1: Vendor: USB Rev: 1.00 Prod: SanDisk 3.2Gen1
Type: Removable Hard Disk
Capacity: 58674.0 MB = 57.2 GB (120164352 x 512)
Pogo_V4> usb tree
USB device tree:
1 Hub (480 Mb/s, 0mA)
u-boot EHCI Host Controller
1 Hub (5 Gb/s, 0mA)
| U-Boot XHCI Host Controller
|
+-2 Mass Storage (480 Mb/s, 200mA)
| SanDisk' Cruzer Fit 03022206021123185243
|
+-3 Mass Storage (5 Gb/s, 224mA)
USB SanDisk 3.2Gen1 0401eab0bfe5e2791483232c55e1640
Pogo_V4>
But move the 2.0 from a rear port to the top port next to the sata port, and I get the USB error:
U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 Model: Cloud Engines PogoPlug Series 4 DRAM: 128 MiB Core: 20 devices, 16 uclasses, devicetree: separate NAND: 128 MiB MMC: mvsdio@90000: 0 Loading Environment from NAND... OK Resetting console stdin/stdout/stderr to serial... In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000 Hit any key to stop autoboot: 0 Pogo_V4> usb start starting USB... Bus ehci@50000: USB EHCI 1.00 Bus xhci_pci: Register 400081f NbrPorts 4 Starting the controller USB XHCI 1.00 scanning bus ehci@50000 for devices... 2 USB Device(s) found scanning bus xhci_pci for devices... XHCI timeout on event type 33... cannot recover. BUG at drivers/usb/host/xhci-ring.c:496/xhci_wait_for_event()! BUG! resetting ... U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 Model: Cloud Engines PogoPlug Series 4 DRAM: 128 MiB Core: 20 devices, 16 uclasses, devicetree: separate NAND: 128 MiB MMC: mvsdio@90000: 0 Loading Environment from NAND... OK Resetting console stdin/stdout/stderr to serial... In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000 Hit any key to stop autoboot: 0 Pogo_V4> usb start starting USB... Bus ehci@50000: USB EHCI 1.00 Bus xhci_pci: Register 400081f NbrPorts 4 Starting the controller USB XHCI 1.00 scanning bus ehci@50000 for devices... 2 USB Device(s) found scanning bus xhci_pci for devices... XHCI timeout on event type 33... cannot recover. BUG at drivers/usb/host/xhci-ring.c:496/xhci_wait_for_event()! BUG! resetting ... U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 Model: Cloud Engines PogoPlug Series 4 DRAM: 128 MiB Core: 20 devices, 16 uclasses, devicetree: separate NAND: 128 MiB MMC: mvsdio@90000: 0 Loading Environment from NAND... OK Resetting console stdin/stdout/stderr to serial... In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000 Hit any key to stop autoboot: 0 Pogo_V4>It probably ties back to the weak top USB port on the device, as you've said before.
Anything else I can provide? I did find a trove of older thumbdrives of 8G or less by various manufacturers if you'd like for me to try those too (initial tests show failures as well, but I wasn't scientific about it).
Edited 2 time(s). Last edit at 07/12/2023 06:24PM by dhargens.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 July 13, 2023 09:31AM |
Admin Registered: 13 years ago Posts: 18,575 |
dhargens,
> Here's something very interesting - when the 3.2
> is in the top rear, and a 2.0 is in the bottom
> rear, it works and shows the following:
>
No, the above test did not work as expected either. Note that you have only 2 USB storage drives. Should be 3 drives.
My test was working fine with 3 drives. So my conclusion is most probably the Sandisk Ultra 3.0 drive has some unknown quirks.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Here's something very interesting - when the 3.2
> is in the top rear, and a 2.0 is in the bottom
> rear, it works and shows the following:
>
U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 > -0700) > Pogoplug V4 > > SoC: Kirkwood 88F6192_A1 > Model: Cloud Engines PogoPlug Series 4 > DRAM: 128 MiB > Core: 20 devices, 16 uclasses, devicetree: > separate > NAND: 128 MiB > MMC: mvsdio@90000: 0 > Loading Environment from NAND... OK > Resetting console stdin/stdout/stderr to > serial... > In: serial > Out: serial > Err: serial > pcie0.0: Link up > Net: eth0: ethernet-controller@72000 > Hit any key to stop autoboot: 0 > Pogo_V4> usb start > starting USB... > Bus ehci@50000: USB EHCI 1.00 > Bus xhci_pci: Register 400081f NbrPorts 4 > Starting the controller > USB XHCI 1.00 > scanning bus ehci@50000 for devices... 1 USB > Device(s) found > scanning bus xhci_pci for devices... 3 USB > Device(s) found > scanning usb for storage devices... 2 > Storage Device(s) found > Pogo_V4> usb storage > Device 0: Vendor: SanDisk' Rev: 1.00 Prod: > Cruzer Fit > Type: Removable Hard Disk > Capacity: 14664.0 MB = 14.3 GB > (30031872 x 512) > Device 1: Vendor: USB Rev: 1.00 Prod: SanDisk > 3.2Gen1 > Type: Removable Hard Disk > Capacity: 58674.0 MB = 57.2 GB > (120164352 x 512) > Pogo_V4> usb tree > USB device tree: > 1 Hub (480 Mb/s, 0mA) > u-boot EHCI Host Controller > > 1 Hub (5 Gb/s, 0mA) > | U-Boot XHCI Host Controller > | > +-2 Mass Storage (480 Mb/s, 200mA) > | SanDisk' Cruzer Fit 03022206021123185243 > | > +-3 Mass Storage (5 Gb/s, 224mA) > USB SanDisk 3.2Gen1 > 0401eab0bfe5e2791483232c55e1640 > > Pogo_V4>>
No, the above test did not work as expected either. Note that you have only 2 USB storage drives. Should be 3 drives.
My test was working fine with 3 drives. So my conclusion is most probably the Sandisk Ultra 3.0 drive has some unknown quirks.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 July 13, 2023 11:20PM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> No, the above test did not work as expected
> either. Note that you have only 2 USB storage
> drives. Should be 3 drives.
>
> My test was working fine with 3 drives. So my
> conclusion is most probably the Sandisk Ultra 3.0
> drive has some unknown quirks.
I could see where I was unclear there - the initial test was using 3 drives, but the following 2 "interesting" sections were with 2 drives alone.
To eliminate the possible Sandisk issue, I set up an 8G Patriot Memory drive with rootfs, an HP 16G data drive, and an 8G data drive branded "PNY" and attempted to boot with those in place. These are all 480 Mb/s drives according to 'usb tree'. This combination errors on 'usb start' as I've described previously.
Top: 8G PNY, data
Rear, top: 8G Patriot, rootfs
Rear, bottom: 16G HP, data
It resets everything and attempts to boot, which I interrupt.
Next, I removed the PNY drive from the top, leaving the HP & Patriot drives in the rear ports.
Top: empty
Rear, top: 8G Patriot, rootfs
Rear, bottom: 16G HP, data
Issuing the command again shows the following:
...which is as expected - 2 drives in the system.
Next, I reinsert the PNY in the top and remove the HP from the rear bottom.
Top: 8G PNY, data
Rear, top: 8G Patriot, rootfs
Rear, bottom: empty
No output - it seems to get lost. I didn't really expect it to work either.
I power-cycle with the drives inserted as described, and it errors again.
None of these drives are 3.x, they're old drives that are probably 1.x speed. I have others I can try, but was trying to be consistant in these tests.
When any 3 drives are in the system and it's booted, no combination of them will work - EXCEPT for one particular drive that will always work if put in the top port. Here's that output after a power cycle:
Top: 8G Kingston, data
Rear, top: 8G Patriot, rootfs
Rear, bottom: 16G HP, data
Again, this is the only time I can make a 3-drive combination work. If the Kingston drive is not in the top, the boot will error due to 'usb start' errors.
I'm confused as to why, because: a) it's not a constant error due to the one case that works, and b) your Sandisks work just fine.
Edited 1 time(s). Last edit at 07/13/2023 11:23PM by dhargens.
-------------------------------------------------------
> No, the above test did not work as expected
> either. Note that you have only 2 USB storage
> drives. Should be 3 drives.
>
> My test was working fine with 3 drives. So my
> conclusion is most probably the Sandisk Ultra 3.0
> drive has some unknown quirks.
I could see where I was unclear there - the initial test was using 3 drives, but the following 2 "interesting" sections were with 2 drives alone.
To eliminate the possible Sandisk issue, I set up an 8G Patriot Memory drive with rootfs, an HP 16G data drive, and an 8G data drive branded "PNY" and attempted to boot with those in place. These are all 480 Mb/s drives according to 'usb tree'. This combination errors on 'usb start' as I've described previously.
Top: 8G PNY, data
Rear, top: 8G Patriot, rootfs
Rear, bottom: 16G HP, data
Pogo_V4> usb start starting USB... Bus ehci@50000: USB EHCI 1.00 Bus xhci_pci: Register 400081f NbrPorts 4 Starting the controller USB XHCI 1.00 scanning bus ehci@50000 for devices... 2 USB Device(s) found scanning bus xhci_pci for devices... XHCI timeout on event type 33... cannot recover. BUG at drivers/usb/host/xhci-ring.c:496/xhci_wait_for_event()! BUG! resetting ...
It resets everything and attempts to boot, which I interrupt.
Next, I removed the PNY drive from the top, leaving the HP & Patriot drives in the rear ports.
Top: empty
Rear, top: 8G Patriot, rootfs
Rear, bottom: 16G HP, data
Issuing the command again shows the following:
Pogo_V4> usb start
starting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 3 USB Device(s) found
scanning usb for storage devices... 2 Storage Device(s) found
Pogo_V4> usb storage
Device 0: Vendor: Rev: PMAP Prod: Patriot Memory
Type: Removable Hard Disk
Capacity: 7640.0 MB = 7.4 GB (15646720 x 512)
Device 1: Vendor: hp Rev: 1100 Prod: v165w
Type: Removable Hard Disk
Capacity: 15334.8 MB = 14.9 GB (31405824 x 512)
Pogo_V4> usb tree
USB device tree:
1 Hub (480 Mb/s, 0mA)
u-boot EHCI Host Controller
1 Hub (5 Gb/s, 0mA)
| U-Boot XHCI Host Controller
|
+-2 Mass Storage (480 Mb/s, 200mA)
| Patriot Memory 07AC0201xxxxxxxxxx
|
+-3 Mass Storage (480 Mb/s, 200mA)
HP v165w AE8FHE0xxxxxxxxxx
Pogo_V4>
...which is as expected - 2 drives in the system.
Next, I reinsert the PNY in the top and remove the HP from the rear bottom.
Top: 8G PNY, data
Rear, top: 8G Patriot, rootfs
Rear, bottom: empty
Pogo_V4> usb start Pogo_V4>
No output - it seems to get lost. I didn't really expect it to work either.
I power-cycle with the drives inserted as described, and it errors again.
None of these drives are 3.x, they're old drives that are probably 1.x speed. I have others I can try, but was trying to be consistant in these tests.
When any 3 drives are in the system and it's booted, no combination of them will work - EXCEPT for one particular drive that will always work if put in the top port. Here's that output after a power cycle:
Pogo_V4> usb start
starting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 2 USB Device(s) found
scanning bus xhci_pci for devices... 3 USB Device(s) found
scanning usb for storage devices... 3 Storage Device(s) found
Pogo_V4> usb storage
Device 0: Vendor: Kingston Rev: 1.00 Prod: DataTraveler 2.0
Type: Removable Hard Disk
Capacity: 7634.9 MB = 7.4 GB (15636304 x 512)
Device 1: Vendor: Rev: PMAP Prod: Patriot Memory
Type: Removable Hard Disk
Capacity: 7640.0 MB = 7.4 GB (15646720 x 512)
Device 2: Vendor: hp Rev: 1100 Prod: v165w
Type: Removable Hard Disk
Capacity: 15334.8 MB = 14.9 GB (31405824 x 512)
Pogo_V4> usb tree
USB device tree:
1 Hub (480 Mb/s, 0mA)
| u-boot EHCI Host Controller
|
+-2 Mass Storage (480 Mb/s, 100mA)
Kingston DataTraveler 2.0 001D0F0C080xxxxxxxxxx
1 Hub (5 Gb/s, 0mA)
| U-Boot XHCI Host Controller
|
+-2 Mass Storage (480 Mb/s, 200mA)
| Patriot Memory 07AC0201xxxxxxxxxx
|
+-3 Mass Storage (480 Mb/s, 200mA)
HP v165w AE8FHE0xxxxxxxxxx
Pogo_V4>
- The ONLY time it WORKS with 3 drives -
Top: 8G Kingston, data
Rear, top: 8G Patriot, rootfs
Rear, bottom: 16G HP, data
Again, this is the only time I can make a 3-drive combination work. If the Kingston drive is not in the top, the boot will error due to 'usb start' errors.
I'm confused as to why, because: a) it's not a constant error due to the one case that works, and b) your Sandisks work just fine.
Edited 1 time(s). Last edit at 07/13/2023 11:23PM by dhargens.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 July 14, 2023 12:33AM |
Admin Registered: 13 years ago Posts: 18,575 |
Hi dhargens,
> Again, this is the only time I can make a
> 3-drive combination work. If the Kingston drive is
> not in the top, the boot will error due to 'usb
> start' errors.
Those were very good tests! I think it's all come down to the top port (USB 2.0) in this box.
>
> I'm confused as to why, because: a) it's not a
> constant error due to the one case that
> works, and b) your Sandisks work just fine.
USB 2.0 drives usually come with very old controller FW. I'd bet that Sandisk Cruzer FIT drive and your Kingston drive FW are relatively new comparing to other brands.
The error you are seeing is the XHCI driver got timed out waiting for its port to report a Completion Status. That fact seems to indicate that the USB 2.0 controller for top port was still busy. And when you use the Kingston drive for the top port it was OK, therefore the Sandisk and the Kingston are "better" drives (perhaps with newer FW).
The XHCI timeout is 5000 ms, so this driver does not look like where the problem is. I think perhaps to really fix this, the EHCI is where it can be improved to handle this corner case..
When I have a chance, I will populate the ZyXEL NSA325 ports to see whether it has similar problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Again, this is the only time I can make a
> 3-drive combination work. If the Kingston drive is
> not in the top, the boot will error due to 'usb
> start' errors.
Those were very good tests! I think it's all come down to the top port (USB 2.0) in this box.
>
> I'm confused as to why, because: a) it's not a
> constant error due to the one case that
> works, and b) your Sandisks work just fine.
USB 2.0 drives usually come with very old controller FW. I'd bet that Sandisk Cruzer FIT drive and your Kingston drive FW are relatively new comparing to other brands.
The error you are seeing is the XHCI driver got timed out waiting for its port to report a Completion Status. That fact seems to indicate that the USB 2.0 controller for top port was still busy. And when you use the Kingston drive for the top port it was OK, therefore the Sandisk and the Kingston are "better" drives (perhaps with newer FW).
The XHCI timeout is 5000 ms, so this driver does not look like where the problem is. I think perhaps to really fix this, the EHCI is where it can be improved to handle this corner case..
When I have a chance, I will populate the ZyXEL NSA325 ports to see whether it has similar problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 July 14, 2023 11:09PM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> Those were very good tests! I think it's all come
> down to the top port (USB 2.0) in this box.
Finally I got you something useful!!
I don't doubt your reasoning a bit - I think it's the top (EHCI) port screwing up too, because 2 drives in the rear ports seem to work fine. If there's a USB
Here's another test using Sandisk drives, which I've been successful with in the past.
Top: empty
Rear, top: 32G Cruzer Ultra 3.2, rootfs
Rear, bottom: 16G Cruzer Fit, data
Looks good. Then, another test to confirm the top port is screwy - move rear bottom to top (EHCI) & recycle power:
Top: 16G Cruzer Fit, data
Rear, top: 32G Cruzer Ultra 3.2, rootfs
Rear, bottom: empty
Epic fail.
Again, I agree that the EHCI is the problem. It then shows itself in blocking or screwing up the reading from the XHCI, which errors and throws the timeout.
Side note: I notice that when 2 drives are in place (in the rear) and show up fine for 'usb start' on boot, if I take out one of the drives and issue the command 'usb start' before cycling the power it shows nothing. I think that's probably minor or to be expected, but I point it out in case that's not how it's expected to be.
-------------------------------------------------------
> Those were very good tests! I think it's all come
> down to the top port (USB 2.0) in this box.
Finally I got you something useful!!
I don't doubt your reasoning a bit - I think it's the top (EHCI) port screwing up too, because 2 drives in the rear ports seem to work fine. If there's a USB
Here's another test using Sandisk drives, which I've been successful with in the past.
Top: empty
Rear, top: 32G Cruzer Ultra 3.2, rootfs
Rear, bottom: 16G Cruzer Fit, data
Pogo_V4> usb start
starting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 3 USB Device(s) found
scanning usb for storage devices... 2 Storage Device(s) found
Pogo_V4> usb storage
Device 0: Vendor: USB Rev: 1.00 Prod: SanDisk 3.2Gen1
Type: Removable Hard Disk
Capacity: 29358.0 MB = 28.6 GB (60125184 x 512)
Device 1: Vendor: SanDisk' Rev: 1.00 Prod: Cruzer Fit
Type: Removable Hard Disk
Capacity: 14664.0 MB = 14.3 GB (30031872 x 512)
Pogo_V4> usb tree
USB device tree:
1 Hub (480 Mb/s, 0mA)
u-boot EHCI Host Controller
1 Hub (5 Gb/s, 0mA)
| U-Boot XHCI Host Controller
|
+-2 Mass Storage (5 Gb/s, 224mA)
| USB SanDisk 3.2Gen1 0501f4b883f7bcd648a4b5fe11dd869
|
+-3 Mass Storage (480 Mb/s, 200mA)
SanDisk' Cruzer Fit 03022206021123185243
Pogo_V4>
Looks good. Then, another test to confirm the top port is screwy - move rear bottom to top (EHCI) & recycle power:
Top: 16G Cruzer Fit, data
Rear, top: 32G Cruzer Ultra 3.2, rootfs
Rear, bottom: empty
Pogo_V4> usb start starting USB... Bus ehci@50000: USB EHCI 1.00 Bus xhci_pci: Register 400081f NbrPorts 4 Starting the controller USB XHCI 1.00 scanning bus ehci@50000 for devices... 2 USB Device(s) found scanning bus xhci_pci for devices... XHCI timeout on event type 33... cannot recover. BUG at drivers/usb/host/xhci-ring.c:496/xhci_wait_for_event()! BUG! resetting ...
Epic fail.
Again, I agree that the EHCI is the problem. It then shows itself in blocking or screwing up the reading from the XHCI, which errors and throws the timeout.
Side note: I notice that when 2 drives are in place (in the rear) and show up fine for 'usb start' on boot, if I take out one of the drives and issue the command 'usb start' before cycling the power it shows nothing. I think that's probably minor or to be expected, but I point it out in case that's not how it's expected to be.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 July 15, 2023 12:33AM |
Registered: 9 years ago Posts: 442 |
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 July 15, 2023 04:46AM |
Admin Registered: 13 years ago Posts: 18,575 |
> Have you confirmed that your power supply is
> actually providing adequate power (12V/2A or 24W)?
> I've experienced USB recognition problems when
> using questionable power supplies in the past.
As I recalled, it is the original power supply came with the box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> actually providing adequate power (12V/2A or 24W)?
> I've experienced USB recognition problems when
> using questionable power supplies in the past.
As I recalled, it is the original power supply came with the box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 August 10, 2023 09:13PM |
Registered: 1 year ago Posts: 81 |
I'm back, and have another problem with a stock uboot on a fresh P4 and trying to boot in any configuration. No matter what I throw at it, it simply will not complete the boot.
Since it's a first time installation on a stock P4, I'm using
instructions posted in https://forum.doozan.com/read.php?2,12096
from the section "Updated 26 Sept 2021", using Debian-5.13.6 (bullseye)
Here's what I've done:
Now to the P4 - I power up, interrupt u-boot count down, and then:
Ok, so that doesn't work. Now I try kwbooting, using the drive formatted as at the top of this message, which has worked fine in the past.
I've tried this on 2 different P4s and I get the same thing.
You'd think as much as I've been futzing with these things I'd have figured out a system to make them work. But no, obviously not.
So where did I go wrong this time?
As always, thanks for the help!
Edited 2 time(s). Last edit at 08/10/2023 10:00PM by dhargens.
Since it's a first time installation on a stock P4, I'm using
instructions posted in https://forum.doozan.com/read.php?2,12096
from the section "Updated 26 Sept 2021", using Debian-5.13.6 (bullseye)
Here's what I've done:
- I clear the drive, make a Linux partition, then format it in ext3 with:
mkfs.ext3 -L rootfs -E lazy_itable_init=0 /dev/sda1
- mount the drive
- untar Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 to mounted drive
- Then I generate the uImage with DTB embedded inside:
setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd' setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000' setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot' setenv bootcmd 'usb reset; run usb_bootcmd; usb stop; reset' [result below] Image Name: Linux-5.13.6-kirkwood-tld-1 Created: Wed Aug 9 23:52:03 2023 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5445794 Bytes = 5318.16 KiB = 5.19 MiB Load Address: 00008000 Entry Point: 00008000I sync a few times, return to root's directory, then umount the drive.
Now to the P4 - I power up, interrupt u-boot count down, and then:
CE>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' CE>> setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' CE>> setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd' CE>> setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000' CE>> setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot' CE>> setenv bootcmd 'usb reset; run usb_bootcmd; usb stop; reset' CE>> printenv baudrate=115200 loads_echo=0 rootpath=/mnt/ARM_FS/ netmask=255.255.0.0 run_diag=yes CASset=min MALLOC_len=1 ethprime=egiga0 load_nand=nboot 0x800000 0 0x200000 load_nand2=nboot 0x800000 0 0x500000 boot=bootm 0x800000 boot_nand=run load_nand boot || run load_nand2 boot ethmtu=1500 usb0Mode=host nandEcc=1bit ethact=egiga0 ethaddr=00:25:31:04:e4:c4 cesvcid=BYC6BP3NVDQNEWFGF43RQ7X6JA ceboardver=PPV4A3 ipaddr=192.168.58.233 serverip=192.168.58.188 bootargs=console=ttyS0,115200 root=ubi0:rootfs ubi.mtd=4,2048 rootfstype=ubifs stdin=serial stdout=serial stderr=serial mainlineLinux=no enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes netbsd_en=no vxworks_en=no bootdelay=1 disaMvPnp=no hddPowerCtrl=no pcieTune=no usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial load_uimage=ext2load usb 0:1 0x800000 /boot/uImage load_uinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd usb_boot=mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000 usb_bootcmd=run usb_set_bootargs; run usb_boot bootcmd=usb reset; run usb_bootcmd; usb stop; reset Environment size: 1206/131068 bytes CE>> boot Unknown command 'usb' - try 'help' ** Block device usb 0 not supported ** Block device usb 0 not supported ## Booting image at 00800000 ... Bad Magic Number Unknown command 'usb' - try 'help' U-Boot 1.1.4 (Oct 1 2011 - 12:06:06) Cloud Engines 1.1.2 (3.4.27) PHYADDR=0...and it starts over again.
Ok, so that doesn't work. Now I try kwbooting, using the drive formatted as at the top of this message, which has worked fine in the past.
$ kwboot -t -B 115200 /dev/ttyAMA0 -b uboot_files/uboot.2017.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...-
Sending boot image...
0 % [......................................................................]
99 % [....................................]
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: MVEBU_MMC: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
Pogov4> printenv dtb_file ethaddr
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethaddr=00:25:31:04:e4:c4
Pogov4> boot
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Reset IDE: ide_preinit failed
Card did not respond to voltage select!
mmc_init: -95, time 15
Partition Map for USB device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 2048 30029824 dd7cbddf-01 83
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
no IDE devices available
Card did not respond to voltage select!
mmc_init: -95, time 14
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 722 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
5445858 bytes read in 921 ms (5.6 MiB/s)
loading uInitrd ...
9671091 bytes read in 896 ms (10.3 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
9970 bytes read in 1876 ms (4.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-5.13.6-kirkwood-tld-1
Created: 2023-08-11 1:58:13 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5445794 Bytes = 5.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-5.13.6-kirkwood-tld-1
Created: 2021-09-24 1:06:32 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9671027 Bytes = 9.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
Booting using the fdt blob at 0x1c00000
Loading Kernel Image ... OK
Loading Ramdisk to 071d0000, end 07b09173 ... OK
Loading Device Tree to 071ca000, end 071cf6f1 ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 5.13.6-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021
[ 0.000000][ T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000][ T0] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: Pogoplug v4
[ 0.000000][ T0] Memory policy: Data cache writeback
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] Normal [mem 0x0000000000000000-0x0000000007ffffff]
[ 0.000000][ T0] Movable zone start for each node
[ 0.000000][ T0] Early memory node ranges
[ 0.000000][ T0] node 0: [mem 0x0000000000000000-0x0000000007ffffff]
[ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 32512
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200
[ 0.000000][ T0] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[ 0.000000][ T0] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.000000][ T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.000000][ T0] Memory: 110556K/131072K available (11264K kernel code, 1553K rwdata, 4272K rodata, 1024K init, 309K bss, 20516K reserved, 0K cma-reserved)
[ 0.000000][ T0] random: get_random_u32 called from ____cache_alloc+0x408/0x7b4 with crng_init=0
[ 0.000000][ T0] trace event string verifier disabled
[ 0.000000][ T0] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000][ T0] Trampoline variant of Tasks RCU enabled.
[ 0.000000][ T0] Tracing variant of Tasks RCU enabled.
[ 0.000000][ T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000][ T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000][ T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[ 0.000003][ T0] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
[ 0.000090][ T0] Switching to timer-based delay loop, resolution 6ns
[ 0.001396][ T0] Console: colour dummy device 80x30
[ 0.001512][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.001574][ T0] pid_max: default: 32768 minimum: 301
[ 0.002181][ T0] LSM: Security Framework initializing
[ 0.002448][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.002521][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.004731][ T0] CPU: Testing write buffer coherency: ok
[ 0.008438][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.008908][ T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.009420][ T1] rcu: Hierarchical SRCU implementation.
[ 0.011681][ T1] devtmpfs: initialized
[ 0.019710][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.019798][ T1] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[ 0.075879][ T1] prandom32: self test passed (less than 6 bits correlated)
[ 0.075949][ T1] prandom: seed boundary self test passed
[ 0.082285][ T1] prandom: 100 self tests passed
[ 0.082332][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.084834][ T1] NET: Registered protocol family 16
[ 0.086015][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.087536][ T1] audit: initializing netlink subsys (disabled)
[ 0.089727][ T1] thermal_sys: Registered thermal governor 'step_wise'
[ 0.090366][ T16] audit: type=2000 audit(0.080:1): state=initialized audit_enabled=0 res=1
[ 0.090614][ T1] cpuidle: using governor ladder
[ 0.090759][ T1] cpuidle: using governor menu
[ 0.091376][ T1] Feroceon L2: Enabling L2
[ 0.091454][ T1] Feroceon L2: Cache support initialised.
[ 0.105085][ T1] No ATAGs?
[ 2.560100][ C0] random: fast init done
[ 7.400037][ T39] "cryptomgr_test" (39) uses obsolete ecb(arc4) skcipher
[ 7.439307][ T59] wait_for_initramfs() called before rootfs_initcalls
[ 7.640291][ T1] raid6: int32x8 gen() 74 MB/s
[ 7.810190][ T1] raid6: int32x8 xor() 46 MB/s
[ 7.980172][ T1] raid6: int32x4 gen() 76 MB/s
[ 8.150306][ T1] raid6: int32x4 xor() 49 MB/s
[ 8.320284][ T1] raid6: int32x2 gen() 97 MB/s
[ 8.490160][ T1] raid6: int32x2 xor() 60 MB/s
[ 8.660346][ T1] raid6: int32x1 gen() 75 MB/s
[ 8.830169][ T1] raid6: int32x1 xor() 43 MB/s
[ 8.830194][ T1] raid6: using algorithm int32x2 gen() 97 MB/s
[ 8.830215][ T1] raid6: .... xor() 60 MB/s, rmw enabled
[ 8.830233][ T1] raid6: using intx1 recovery algorithm
[ 8.830650][ T1] vgaarb: loaded
[ 8.831505][ T1] SCSI subsystem initialized
[ 8.832296][ T1] usbcore: registered new interface driver usbfs
[ 8.832422][ T1] usbcore: registered new interface driver hub
[ 8.832508][ T1] usbcore: registered new device driver usb
[ 8.832821][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 8.832845][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 8.832896][ T1] PTP clock support registered
[ 8.835496][ T1] clocksource: Switched to clocksource orion_clocksource
[ 8.986510][ T1] VFS: Disk quotas dquot_6.6.0
[ 8.986671][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 9.009626][ T1] NET: Registered protocol family 2
[ 9.009876][ T1] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 9.011269][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 9.011345][ T1] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 9.011397][ T1] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 9.011440][ T1] TCP: Hash tables configured (established 1024 bind 1024)
[ 9.011847][ T1] MPTCP token hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 9.011961][ T1] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 9.012024][ T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 9.012369][ T1] NET: Registered protocol family 1
[ 9.026120][ T1] RPC: Registered named UNIX socket transport module.
[ 9.026157][ T1] RPC: Registered udp transport module.
[ 9.026176][ T1] RPC: Registered tcp transport module.
[ 9.026194][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 9.026221][ T1] PCI: CLS 0 bytes, default 32
[ 9.026350][ T1] NetWinder Floating Point Emulator V0.97 (double precision)
[ 11.248426][ T1] Initialise system trusted keyrings
[ 11.248537][ T1] Key type blacklist registered
[ 11.248941][ T1] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[ 11.249120][ T1] zbud: loaded
[ 11.251389][ T1] NFS: Registering the id_resolver key type
[ 11.251454][ T1] Key type id_resolver registered
[ 11.251476][ T1] Key type id_legacy registered
[ 11.251546][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 11.251582][ T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 11.251606][ T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 11.252017][ T1] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 11.252848][ T1] fuse: init (API version 7.34)
[ 11.253449][ T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 11.253785][ T1] orangefs_init: module version upstream loaded
[ 11.253816][ T1] SGI XFS with ACLs, security attributes, realtime, scrub, quota, no debug enabled
[ 11.404458][ T1] xor: measuring software checksum speed
[ 11.417951][ T1] arm4regs : 739 MB/sec
[ 11.440069][ T1] 8regs : 447 MB/sec
[ 11.455272][ T1] 32regs : 651 MB/sec
[ 11.455298][ T1] xor: using function: arm4regs (739 MB/sec)
[ 11.455331][ T1] async_tx: api initialized (async)
[ 11.455362][ T1] Key type asymmetric registered
[ 11.455382][ T1] Asymmetric key parser 'x509' registered
[ 11.455474][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 11.455644][ T1] io scheduler bfq registered
[ 11.753078][ T1] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 47
[ 11.753125][ T1] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 49
[ 11.753704][ T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 11.756653][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[ 11.756789][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[ 11.756859][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 11.756911][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 11.757371][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 11.757409][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 11.757446][ T1] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[ 11.757479][ T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 11.757508][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 11.757693][ T1] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[ 11.757751][ T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 11.759439][ T1] PCI: bus0: Fast back to back transfers disabled
[ 11.759494][ T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 11.759835][ T1] pci 0000:01:00.0: [1b73:1009] type 00 class 0x0c0330
[ 11.759892][ T1] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit]
[ 11.759938][ T1] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x00000fff 64bit]
[ 11.759981][ T1] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x00000fff 64bit]
[ 11.760115][ T1] pci 0000:01:00.0: supports D1
[ 11.760143][ T1] pci 0000:01:00.0: PME# supported from D0 D1 D3hot
[ 11.760252][ T1] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:01.0 (capable of 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
[ 11.786874][ T1] PCI: bus1: Fast back to back transfers disabled
[ 11.786925][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 11.787250][ T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[ 11.787293][ T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0100000-0xe01007ff pref]
[ 11.787336][ T1] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe000ffff 64bit]
[ 11.787382][ T1] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0010000-0xe0010fff 64bit]
[ 11.787426][ T1] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0011000-0xe0011fff 64bit]
[ 11.787470][ T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 11.787503][ T1] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 11.787692][ T1] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[ 11.787838][ T1] pci 0000:01:00.0: enabling device (0140 -> 0142)
[ 11.788670][ T1] mv_xor f1060800.xor: Marvell shared XOR driver
[ 11.847167][ T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 11.851137][ T1] mv_xor f1060900.xor: Marvell shared XOR driver
[ 11.917145][ T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 11.921544][ T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 11.923695][ T1] printk: console [ttyS0] disabled
[ 11.923842][ T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 25, base_baud = 10416666) is a 16550A
[ 13.008418][ T1] printk: console [ttyS0] enabled
[ 13.026595][ T1] loop: module loaded
[ 13.031667][ T1] sata_mv f1080000.sata: slots 32 ports 2
[ 13.042952][ T1] scsi host0: sata_mv
[ 13.047863][ T1] scsi host1: sata_mv
[ 13.052093][ T1] ata1: SATA max UDMA/133 irq 32
[ 13.056963][ T1] ata2: SATA max UDMA/133 irq 32
[ 13.063293][ T1] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 13.070381][ T1] nand: Hynix H27U1G8F2BTR-BC
[ 13.074907][ T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 13.083624][ T1] Scanning device for bad blocks
[ 13.189588][ T1] 5 fixed-partitions partitions found on MTD device orion_nand
[ 13.197002][ T1] Creating 5 MTD partitions on "orion_nand":
[ 13.202828][ T1] 0x000000000000-0x000000200000 : "u-boot"
[ 13.210851][ T1] 0x000000200000-0x000000500000 : "uImage"
[ 13.218783][ T1] 0x000000500000-0x000000800000 : "uImage2"
[ 13.226775][ T1] 0x000000800000-0x000001000000 : "failsafe"
[ 13.234775][ T1] 0x000001000000-0x000008000000 : "root"
[ 13.243956][ T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[ 13.252527][ T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[ 13.264636][ T1] libphy: Fixed MDIO Bus: probed
[ 13.271742][ T1] libphy: orion_mdio_bus: probed
[ 13.278944][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 13.388071][ T94] ata1: SATA link down (SStatus 0 SControl F300)
[ 13.737299][ T96] ata2: SATA link down (SStatus 0 SControl F300)
[ 14.046996][ T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:04:e4:c4
[ 14.056654][ T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 14.063900][ T1] ehci-pci: EHCI PCI platform driver
[ 14.069149][ T1] ehci-orion: EHCI orion driver
[ 14.074170][ T1] orion-ehci f1050000.ehci: EHCI Host Controller
[ 14.080429][ T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 14.089245][ T1] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[ 14.125545][ T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 14.132664][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.13
[ 14.141652][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 14.149579][ T1] usb usb1: Product: EHCI Host Controller
[ 14.155142][ T1] usb usb1: Manufacturer: Linux 5.13.6-kirkwood-tld-1 ehci_hcd
[ 14.162547][ T1] usb usb1: SerialNumber: f1050000.ehci
[ 14.168997][ T1] hub 1-0:1.0: USB hub found
[ 14.173502][ T1] hub 1-0:1.0: 1 port detected
[ 14.179525][ T1] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 14.185466][ T1] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[ 14.195392][ T1] xhci_hcd 0000:01:00.0: hcc params 0x200073a1 hci version 0x100 quirks 0x0000000000080010
[ 14.206311][ T1] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.13
[ 14.215261][ T1] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 14.223195][ T1] usb usb2: Product: xHCI Host Controller
[ 14.228791][ T1] usb usb2: Manufacturer: Linux 5.13.6-kirkwood-tld-1 xhci-hcd
[ 14.236194][ T1] usb usb2: SerialNumber: 0000:01:00.0
[ 14.242458][ T1] hub 2-0:1.0: USB hub found
[ 14.247052][ T1] hub 2-0:1.0: 2 ports detected
[ 14.252743][ T1] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 14.258785][ T1] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[ 14.266930][ T1] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[ 14.274017][ T1] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 14.283298][ T1] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.13
[ 14.292278][ T1] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 14.300208][ T1] usb usb3: Product: xHCI Host Controller
[ 14.305797][ T1] usb usb3: Manufacturer: Linux 5.13.6-kirkwood-tld-1 xhci-hcd
[ 14.313176][ T1] usb usb3: SerialNumber: 0000:01:00.0
[ 14.319630][ T1] hub 3-0:1.0: USB hub found
[ 14.324138][ T1] hub 3-0:1.0: 2 ports detected
[ 14.330291][ T1] usbcore: registered new interface driver usb-storage
[ 14.337747][ T1] mousedev: PS/2 mouse device common for all mice
[ 14.465538][ T17] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 14.666625][ T17] usb 1-1: New USB device found, idVendor=0781, idProduct=5571, bcdDevice= 1.00
[ 14.675528][ T17] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 14.683376][ T17] usb 1-1: Product: Cruzer Fit
[ 14.688022][ T17] usb 1-1: Manufacturer: SanDisk'
[ 14.692897][ T17] usb 1-1: SerialNumber: 03022208021123185156
[ 14.699946][ T17] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 14.707699][ T17] scsi host2: usb-storage 1-1:1.0
[ 15.365543][ T1] rtc-mv f1010300.rtc: internal RTC not ticking
[ 15.371896][ T1] i2c /dev entries driver
[ 15.377078][ T1] device-mapper: uevent: version 1.0.3
[ 15.382817][ T1] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: dm-devel@redhat.com
[ 15.392646][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 15.399947][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 15.407284][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 15.414674][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 15.421479][ T1] device-mapper: raid: Loading target version 1.15.1
[ 15.430088][ T1] hid: raw HID events driver (C) Jiri Kosina
[ 15.436431][ T1] drop_monitor: Initializing network drop monitor service
[ 15.444080][ T1] NET: Registered protocol family 10
[ 15.451364][ T1] Segment Routing with IPv6
[ 15.455857][ T1] RPL Segment Routing with IPv6
[ 15.460688][ T1] NET: Registered protocol family 17
[ 15.466238][ T1] Key type dns_resolver registered
[ 15.471902][ T1] registered taskstats version 1
[ 15.476798][ T1] Loading compiled-in X.509 certificates
[ 15.482961][ T1] zswap: loaded using pool lzo/zbud
[ 15.488637][ T1] Key type ._fscrypt registered
[ 15.493339][ T1] Key type .fscrypt registered
[ 15.498050][ T1] Key type fscrypt-provisioning registered
[ 15.507346][ T1] Key type big_key registered
[ 15.517759][ T1] Key type encrypted registered
[ 15.527566][ T1] md: Waiting for all devices to be available before autodetect
[ 15.535045][ T1] md: If you don't use raid, use raid=noautodetect
[ 15.541608][ T1] md: Autodetecting RAID arrays.
[ 15.546502][ T1] md: autorun ...
[ 15.549982][ T1] md: ... autorun DONE.
[ 15.555055][ T1] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 15.563347][ T1] Please append a correct "root=" boot option; here are the available partitions:
[ 15.572497][ T1] 1f00 2048 mtdblock0
[ 15.572513][ T1] (driver?)
[ 15.580501][ T1] 1f01 3072 mtdblock1
[ 15.580516][ T1] (driver?)
[ 15.588481][ T1] 1f02 3072 mtdblock2
[ 15.588495][ T1] (driver?)
[ 15.596467][ T1] 1f03 8192 mtdblock3
[ 15.596483][ T1] (driver?)
[ 15.604396][ T1] 1f04 114688 mtdblock4
[ 15.604409][ T1] (driver?)
[ 15.612374][ T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 15.621308][ T1] CPU: 0 PID: 1 Comm: swapper Not tainted 5.13.6-kirkwood-tld-1 #1.0
[ 15.629201][ T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[ 15.636155][ T1] [<8010e0a4>] (unwind_backtrace) from [<8010a8ac>] (show_stack+0x10/0x14)
[ 15.644602][ T1] [<8010a8ac>] (show_stack) from [<80afddf4>] (panic+0xfc/0x328)
[ 15.652180][ T1] [<80afddf4>] (panic) from [<81101ad0>] (mount_block_root+0x1e0/0x26c)
[ 15.660352][ T1] [<81101ad0>] (mount_block_root) from [<81101c4c>] (mount_root+0xf0/0x120)
[ 15.668870][ T1] [<81101c4c>] (mount_root) from [<81101dc0>] (prepare_namespace+0x144/0x180)
[ 15.677553][ T1] [<81101dc0>] (prepare_namespace) from [<811015e4>] (kernel_init_freeable+0x1d0/0x234)
[ 15.687100][ T1] [<811015e4>] (kernel_init_freeable) from [<80b091cc>] (kernel_init+0x8/0x118)
[ 15.695964][ T1] [<80b091cc>] (kernel_init) from [<80100148>] (ret_from_fork+0x14/0x2c)
[ 15.704224][ T1] Exception stack(0x814a5fb0 to 0x814a5ff8)
[ 15.709956][ T1] 5fa0: 00000000 00000000 00000000 00000000
[ 15.718806][ T1] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 15.727651][ T1] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 15.734956][ T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
I get a kernel panic whether I have an ext3 or ext4 rootfs in place for booting.
I've tried this on 2 different P4s and I get the same thing.
You'd think as much as I've been futzing with these things I'd have figured out a system to make them work. But no, obviously not.
So where did I go wrong this time?
As always, thanks for the help!
Edited 2 time(s). Last edit at 08/10/2023 10:00PM by dhargens.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 August 11, 2023 01:18AM |
Admin Registered: 13 years ago Posts: 18,575 |
dhargens,
> mkfs.ext3 -L rootfs -E lazy_itable_init=0 /dev/sda1
No need to have extra option.That should be:
> CE>> boot
> Unknown command 'usb' - try 'help'
>
> ** Block device usb 0 not supported
The error is because stock u-boot does not support USB commands.
> Ok, so that doesn't work. Now I try kwbooting,
> using the drive formatted as at the top of this
> message, which has worked fine in the past.
Use the same USB 2.0 rootfs from one of your operational Pogo V4's. Since you are kwboot'ing with 2017.07 u-boot version, this rootfs should have the original uImage.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> mkfs.ext3 -L rootfs -E lazy_itable_init=0 /dev/sda1
No need to have extra option.That should be:
mkfs.ext3 -L rootfs /dev/sda1 sync
> CE>> boot
> Unknown command 'usb' - try 'help'
>
> ** Block device usb 0 not supported
The error is because stock u-boot does not support USB commands.
> Ok, so that doesn't work. Now I try kwbooting,
> using the drive formatted as at the top of this
> message, which has worked fine in the past.
Use the same USB 2.0 rootfs from one of your operational Pogo V4's. Since you are kwboot'ing with 2017.07 u-boot version, this rootfs should have the original uImage.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
