* WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
@ 2020-12-14 8:03 David Schaefer
2020-12-14 13:36 ` Richard Weinberger
0 siblings, 1 reply; 16+ messages in thread
From: David Schaefer @ 2020-12-14 8:03 UTC (permalink / raw)
To: linux-mtd
Hi,
I am trying to upgrade to a more recent kernel. I face the issue that
I am missing the /dev/mtdblock1-6 devices. I have tracked down that
issue shows up the first time with 4.16.1 and does not exist with
4.15.18.
Also I have this initalization during 4.15.18:
> f10d0000.nand: This platform can't do DMA on this device
> nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
> nand: Hynix H27U2G8F2CTR-BC
> nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048
> Bad block table found at page 131008, version 0x01
> Bad block table found at page 130944, version 0x01
> nand_read_bbt: bad block at 0x00000e7c0000
> 7 ofpart partitions found on MTD device pxa3xx_nand-0
> Creating 7 MTD partitions on "pxa3xpxa3xx-nand x_nand-0":
> 0x000000000000-0x000000500000 : "u-Boot"
> 0x000000500000-0x000000a00000 : "uImage"
> 0x000000a00000-0x000000f00000 : "ramdisk"
> 0x000000f00000-0x00000d800000 : "image.cfs"
> 0x00000dd00000-0x00000ec00000 : "rescue firmware"
> 0x00000ec00000-0x000010000000 : "config"
> 0x00000d800000-0x00000dd00000 : "reserve"
and this with 4.16.1:
> nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
> nand: Hynix H27U2G8F2CTR-BC
> nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> marvell-nfc f10d0000.nand: Timeout on CMDD (NDSR: 0x00000080)
> marvell-nfc f10d0000.nand: Timeout on CMDD (NDSR: 0x00000280)
> Bad block table not found for chip 0
> Bad block table not found for chip 0
> Scanning device for bad blocks
> Bad eraseblock 1854 at 0x00000e7c0000
I have tried 4.19.161 and 5.4.83 as well but my /dev/mtdblock1-6
devices keep being missing.
What do I have to do to turn them back on? Do I have to modify my dts
file for the new driver marvell_nand?
https://fox-exe.ru/WDMyCloud/WDMyCloud-Mirror/Developing/kernel-4.15.0-rc6/armada-370-wdmc-mirror-gen1.dts
I've read whatever I found and do not know how to continue here.
Kind regards
David
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-14 8:03 WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc David Schaefer
@ 2020-12-14 13:36 ` Richard Weinberger
2020-12-14 14:58 ` David Schaefer
0 siblings, 1 reply; 16+ messages in thread
From: Richard Weinberger @ 2020-12-14 13:36 UTC (permalink / raw)
To: David Schaefer; +Cc: linux-mtd, Miquel Raynal
David,
On Mon, Dec 14, 2020 at 9:08 AM David Schaefer
<david.tillmann.schaefer@gmail.com> wrote:
>
> Hi,
>
> I am trying to upgrade to a more recent kernel. I face the issue that
> I am missing the /dev/mtdblock1-6 devices. I have tracked down that
> issue shows up the first time with 4.16.1 and does not exist with
> 4.15.18.
>
> Also I have this initalization during 4.15.18:
>
> > f10d0000.nand: This platform can't do DMA on this device
> > nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
> > nand: Hynix H27U2G8F2CTR-BC
> > nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> > pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048
> > Bad block table found at page 131008, version 0x01
> > Bad block table found at page 130944, version 0x01
> > nand_read_bbt: bad block at 0x00000e7c0000
> > 7 ofpart partitions found on MTD device pxa3xx_nand-0
> > Creating 7 MTD partitions on "pxa3xpxa3xx-nand x_nand-0":
> > 0x000000000000-0x000000500000 : "u-Boot"
> > 0x000000500000-0x000000a00000 : "uImage"
> > 0x000000a00000-0x000000f00000 : "ramdisk"
> > 0x000000f00000-0x00000d800000 : "image.cfs"
> > 0x00000dd00000-0x00000ec00000 : "rescue firmware"
> > 0x00000ec00000-0x000010000000 : "config"
> > 0x00000d800000-0x00000dd00000 : "reserve"
>
> and this with 4.16.1:
>
> > nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
> > nand: Hynix H27U2G8F2CTR-BC
> > nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> > marvell-nfc f10d0000.nand: Timeout on CMDD (NDSR: 0x00000080)
> > marvell-nfc f10d0000.nand: Timeout on CMDD (NDSR: 0x00000280)
> > Bad block table not found for chip 0
> > Bad block table not found for chip 0
> > Scanning device for bad blocks
> > Bad eraseblock 1854 at 0x00000e7c0000
>
> I have tried 4.19.161 and 5.4.83 as well but my /dev/mtdblock1-6
> devices keep being missing.
>
> What do I have to do to turn them back on? Do I have to modify my dts
> file for the new driver marvell_nand?
> https://fox-exe.ru/WDMyCloud/WDMyCloud-Mirror/Developing/kernel-4.15.0-rc6/armada-370-wdmc-mirror-gen1.dts
Enabling CONFIG_MTD_NAND_MARVELL should give you the new marvell driver.
IIRC no changes to the dts are needed. Though, there have been some
fixes such as:
f6997bec6af4 ("mtd: rawnand: marvell: fix the chip-select DT parsing logic")
Do you see this failure with both the old and the new marvell drivers?
Maybe Miquel has an idea too.
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-14 13:36 ` Richard Weinberger
@ 2020-12-14 14:58 ` David Schaefer
2020-12-14 15:20 ` Richard Weinberger
0 siblings, 1 reply; 16+ messages in thread
From: David Schaefer @ 2020-12-14 14:58 UTC (permalink / raw)
To: Richard Weinberger; +Cc: linux-mtd, Miquel Raynal
Hi Richard,
Am Mo., 14. Dez. 2020 um 14:36 Uhr schrieb Richard Weinberger
<richard.weinberger@gmail.com>:
>
> David,
>
> On Mon, Dec 14, 2020 at 9:08 AM David Schaefer
> <david.tillmann.schaefer@gmail.com> wrote:
> >
> > Hi,
> >
> > I am trying to upgrade to a more recent kernel. I face the issue that
> > I am missing the /dev/mtdblock1-6 devices. I have tracked down that
> > issue shows up the first time with 4.16.1 and does not exist with
> > 4.15.18.
> >
> > Also I have this initalization during 4.15.18:
> >
> > > f10d0000.nand: This platform can't do DMA on this device
> > > nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
> > > nand: Hynix H27U2G8F2CTR-BC
> > > nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> > > pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048
> > > Bad block table found at page 131008, version 0x01
> > > Bad block table found at page 130944, version 0x01
> > > nand_read_bbt: bad block at 0x00000e7c0000
> > > 7 ofpart partitions found on MTD device pxa3xx_nand-0
> > > Creating 7 MTD partitions on "pxa3xpxa3xx-nand x_nand-0":
> > > 0x000000000000-0x000000500000 : "u-Boot"
> > > 0x000000500000-0x000000a00000 : "uImage"
> > > 0x000000a00000-0x000000f00000 : "ramdisk"
> > > 0x000000f00000-0x00000d800000 : "image.cfs"
> > > 0x00000dd00000-0x00000ec00000 : "rescue firmware"
> > > 0x00000ec00000-0x000010000000 : "config"
> > > 0x00000d800000-0x00000dd00000 : "reserve"
> >
> > and this with 4.16.1:
> >
> > > nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
> > > nand: Hynix H27U2G8F2CTR-BC
> > > nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> > > marvell-nfc f10d0000.nand: Timeout on CMDD (NDSR: 0x00000080)
> > > marvell-nfc f10d0000.nand: Timeout on CMDD (NDSR: 0x00000280)
> > > Bad block table not found for chip 0
> > > Bad block table not found for chip 0
> > > Scanning device for bad blocks
> > > Bad eraseblock 1854 at 0x00000e7c0000
> >
> > I have tried 4.19.161 and 5.4.83 as well but my /dev/mtdblock1-6
> > devices keep being missing.
> >
> > What do I have to do to turn them back on? Do I have to modify my dts
> > file for the new driver marvell_nand?
> > https://fox-exe.ru/WDMyCloud/WDMyCloud-Mirror/Developing/kernel-4.15.0-rc6/armada-370-wdmc-mirror-gen1.dts
>
> Enabling CONFIG_MTD_NAND_MARVELL should give you the new marvell driver.
> IIRC no changes to the dts are needed. Though, there have been some
> fixes such as:
> f6997bec6af4 ("mtd: rawnand: marvell: fix the chip-select DT parsing logic")
>
> Do you see this failure with both the old and the new marvell drivers?
>
> Maybe Miquel has an idea too.
I have checked the kernel configuration. For 4.15.18 I have these settings:
CONFIG_MTD_NAND_ECC=y
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_PXA3xx=y
and for 4.16.1
CONFIG_MTD_NAND_ECC=y
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_MARVELL=y
I actually copied the working configuration from 4.15.18 to 4.16.1,
did make oldconfig, and compiled it the same way as 4.15.18. Like I
said above, 4.15 works, 4.16 does not.
I hope this answers your question whether I see the issue with the new
and the old marvell drivers because I am not 100% sure what you refer
to here (I guess you mean PXA3XX vs NAND).
Kind regards
David
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-14 14:58 ` David Schaefer
@ 2020-12-14 15:20 ` Richard Weinberger
2020-12-14 17:16 ` David Schaefer
0 siblings, 1 reply; 16+ messages in thread
From: Richard Weinberger @ 2020-12-14 15:20 UTC (permalink / raw)
To: David Schaefer; +Cc: linux-mtd, Miquel Raynal
David,
----- Ursprüngliche Mail -----
> I have checked the kernel configuration. For 4.15.18 I have these settings:
> CONFIG_MTD_NAND_ECC=y
> CONFIG_MTD_NAND=y
> CONFIG_MTD_NAND_PXA3xx=y
>
> and for 4.16.1
>
> CONFIG_MTD_NAND_ECC=y
> CONFIG_MTD_NAND=y
> CONFIG_MTD_NAND_MARVELL=y
>
> I actually copied the working configuration from 4.15.18 to 4.16.1,
> did make oldconfig, and compiled it the same way as 4.15.18. Like I
> said above, 4.15 works, 4.16 does not.
> I hope this answers your question whether I see the issue with the new
> and the old marvell drivers because I am not 100% sure what you refer
> to here (I guess you mean PXA3XX vs NAND).
Ah, right. I forgot that the old driver got removed. I thought we kept it for a few releases. ;-\
So there is a regression.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-14 15:20 ` Richard Weinberger
@ 2020-12-14 17:16 ` David Schaefer
2020-12-14 21:24 ` Richard Weinberger
2020-12-15 15:50 ` David Schaefer
0 siblings, 2 replies; 16+ messages in thread
From: David Schaefer @ 2020-12-14 17:16 UTC (permalink / raw)
To: Richard Weinberger; +Cc: linux-mtd, Miquel Raynal
If this is a regression, how can we continue here? Can I give hardware
specs and logs? I have soldered on the board to access UART. I can
provide e.g. boot logs.
/David
Am Mo., 14. Dez. 2020 um 16:20 Uhr schrieb Richard Weinberger <richard@nod.at>:
>
> David,
>
> ----- Ursprüngliche Mail -----
> > I have checked the kernel configuration. For 4.15.18 I have these settings:
> > CONFIG_MTD_NAND_ECC=y
> > CONFIG_MTD_NAND=y
> > CONFIG_MTD_NAND_PXA3xx=y
> >
> > and for 4.16.1
> >
> > CONFIG_MTD_NAND_ECC=y
> > CONFIG_MTD_NAND=y
> > CONFIG_MTD_NAND_MARVELL=y
> >
> > I actually copied the working configuration from 4.15.18 to 4.16.1,
> > did make oldconfig, and compiled it the same way as 4.15.18. Like I
> > said above, 4.15 works, 4.16 does not.
> > I hope this answers your question whether I see the issue with the new
> > and the old marvell drivers because I am not 100% sure what you refer
> > to here (I guess you mean PXA3XX vs NAND).
>
> Ah, right. I forgot that the old driver got removed. I thought we kept it for a few releases. ;-\
> So there is a regression.
>
> Thanks,
> //richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-14 17:16 ` David Schaefer
@ 2020-12-14 21:24 ` Richard Weinberger
2020-12-14 23:03 ` Miquel Raynal
2020-12-15 15:50 ` David Schaefer
1 sibling, 1 reply; 16+ messages in thread
From: Richard Weinberger @ 2020-12-14 21:24 UTC (permalink / raw)
To: David Schaefer; +Cc: linux-mtd, Miquel Raynal
On Mon, Dec 14, 2020 at 6:22 PM David Schaefer
<david.tillmann.schaefer@gmail.com> wrote:
>
> If this is a regression, how can we continue here? Can I give hardware
> specs and logs? I have soldered on the board to access UART. I can
> provide e.g. boot logs.
No need to worry. Let's wait for Miquel, I'm sure he has an idea.
In the absolute worst case we reconstruct the old driver.
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-14 21:24 ` Richard Weinberger
@ 2020-12-14 23:03 ` Miquel Raynal
2020-12-15 10:14 ` David Schaefer
0 siblings, 1 reply; 16+ messages in thread
From: Miquel Raynal @ 2020-12-14 23:03 UTC (permalink / raw)
To: Richard Weinberger; +Cc: David Schaefer, linux-mtd
Hello,
Richard Weinberger <richard.weinberger@gmail.com> wrote on Mon, 14 Dec
2020 22:24:24 +0100:
> On Mon, Dec 14, 2020 at 6:22 PM David Schaefer
> <david.tillmann.schaefer@gmail.com> wrote:
> >
> > If this is a regression, how can we continue here? Can I give hardware
> > specs and logs? I have soldered on the board to access UART. I can
> > provide e.g. boot logs.
>
> No need to worry. Let's wait for Miquel, I'm sure he has an idea.
> In the absolute worst case we reconstruct the old driver.
>
Yes indeed, this looks like a regression but I bet we already fixed it.
Perhaps there has been a backporting issue and we did not spot it.
Can you please try the following fixes (in this order):
f6997bec6af4 mtd: rawnand: marvell: fix the chip-select DT parsing logic
b76401fc4ba7 mtd: rawnand: marvell: pass ms delay to wait_op
a2ee41fd953e mtd: rawnand: marvell: fix command xtype in BCH write hook
90d617633368 mtd: rawnand: marvell: Fix read logic for layouts with ->nchunks > 2
7fd130f7416f mtd: rawnand: marvell: support 8b/512B strength for 2kiB pages layout
53c83b59759c mtd: rawnand: marvell: fix the IRQ handler complete() condition
cafb56dd741e mtd: rawnand: marvell: prevent timeouts on a loaded machine
c27075772d1f mtd: rawnand: marvell: Fix the condition on a return code
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-14 23:03 ` Miquel Raynal
@ 2020-12-15 10:14 ` David Schaefer
0 siblings, 0 replies; 16+ messages in thread
From: David Schaefer @ 2020-12-15 10:14 UTC (permalink / raw)
To: Miquel Raynal; +Cc: Richard Weinberger, linux-mtd
Hi Miquel,
Am Di., 15. Dez. 2020 um 00:03 Uhr schrieb Miquel Raynal
<miquel.raynal@bootlin.com>:
> > > If this is a regression, how can we continue here? Can I give hardware
> > > specs and logs? I have soldered on the board to access UART. I can
> > > provide e.g. boot logs.
> >
> > No need to worry. Let's wait for Miquel, I'm sure he has an idea.
> > In the absolute worst case we reconstruct the old driver.
> >
>
> Yes indeed, this looks like a regression but I bet we already fixed it.
> Perhaps there has been a backporting issue and we did not spot it.
> Can you please try the following fixes (in this order):
> f6997bec6af4 mtd: rawnand: marvell: fix the chip-select DT parsing logic
> b76401fc4ba7 mtd: rawnand: marvell: pass ms delay to wait_op
> a2ee41fd953e mtd: rawnand: marvell: fix command xtype in BCH write hook
> 90d617633368 mtd: rawnand: marvell: Fix read logic for layouts with ->nchunks > 2
> 7fd130f7416f mtd: rawnand: marvell: support 8b/512B strength for 2kiB pages layout
> 53c83b59759c mtd: rawnand: marvell: fix the IRQ handler complete() condition
> cafb56dd741e mtd: rawnand: marvell: prevent timeouts on a loaded machine
> c27075772d1f mtd: rawnand: marvell: Fix the condition on a return code
Thank you for your suggested commits. I guess you are right and the
issue already
has been fixed. I am not sure which commit is working for production
so I have attached
the boot logs for all kernels that I obtained by cherry-picking your
suggested commits from
top to bottom, one by one. Please note that there was a merge conflict
when merging
7fd130f7416f that I solved by '-X theirs'.
Kind regards
David
------------- cherry-pick f6997bec6af4
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
-> does not continue booting
------------- cherry-pick b76401fc4ba7
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error while writing BBT block -110
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error -110 while marking block 2047 bad
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error while writing BBT block -110
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
ata1: SATA link down (SStatus 0 SControl F300)
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error -110 while marking block 2046 bad
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error while writing BBT block -110
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error -110 while marking block 2045 bad
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error while writing BBT block -110
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error -110 while marking block 2044 bad
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error while writing BBT block -110
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error -110 while marking block 2043 bad
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error while writing BBT block -110
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error -110 while marking block 2042 bad
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error while writing BBT block -110
ata2: SATA link down (SStatus 0 SControl F300)
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error -110 while marking block 2041 bad
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error while writing BBT block -110
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
marvell-nfc f10d0000.nand: Timeout waiting for RB signal
nand_bbt: error -110 while marking block 2040 bad
No space left to write bad block table
nand_bbt: error while writing bad block table -28
marvell-nfc f10d0000.nand: nand_scan_tail failed: -28
marvell-nfc: probe of f10d0000.nand failed with error -28
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
libphy: Fixed MDIO Bus: probed
libphy: orion_mdio_bus: probed
mvneta f1074000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
usbcore: registered new interface driver lan78xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.usb: EHCI Host Controller
orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.16.0+ ehci_hcd
usb usb1: SerialNumber: f1050000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
rtc-mv f1010300.rtc: internal RTC not ticking
i2c /dev entries driver
device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
marvell-cesa f1090000.crypto: CESA device successfully registered
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
Loading compiled-in X.509 certificates
armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
input: gpio-keys as /devices/platform/gpio-keys/input/input0
hctosys: unable to open rtc device (rtc0)
Freeing unused kernel memory: 1024K
# Loading, please wait...
# Mounting filesystems...
# Check disk and init
### Press any key to stop and run shell... (2)mdadm: No arrays found
in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
mvneta f1074000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver
[Marvell 88E1510]
mvneta f1074000.ethernet eth0: configuring for phy/rgmii-id link mode
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending discover...
mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.178.59...
Lease of 192.168.178.59 obtained, lease time 864000
Setting IP address 192.168.178.59 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending select for 192.168.178.59...
Lease of 192.168.178.59 obtained, lease time 864000
Setting IP address 192.168.178.59 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
/ # ls /dev/mtd*
ls: /dev/mtd*: No such file or directory
------------- cherry-pick a2ee41fd953e
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
Bad block table written to 0x00000ffe0000, version 0x01
Bad block table written to 0x00000ffc0000, version 0x01
7 ofpart partitions found on MTD device pxa3xx_nand-0
Creating 7 MTD partitions on "pxa3xx_nand-0":
0x000000000000-0x000000500000 : "u-Boot"
0x000000500000-0x000000a00000 : "uImage"
0x000000a00000-0x000000f00000 : "ramdisk"
0x000000f00000-0x00000d800000 : "image.cfs"
0x00000dd00000-0x00000ec00000 : "rescue firmware"
0x00000ec00000-0x000010000000 : "config"
0x00000d800000-0x00000dd00000 : "reserve"
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
libphy: Fixed MDIO Bus: probed
libphy: orion_mdio_bus: probed
mvneta f1074000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
usbcore: registered new interface driver lan78xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.usb: EHCI Host Controller
orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
ata1: SATA link down (SStatus 0 SControl F300)
orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.16.0+ ehci_hcd
usb usb1: SerialNumber: f1050000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
ata2: SATA link down (SStatus 0 SControl F300)
rtc-mv f1010300.rtc: internal RTC not ticking
i2c /dev entries driver
device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
marvell-cesa f1090000.crypto: CESA device successfully registered
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
Loading compiled-in X.509 certificates
armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
input: gpio-keys as /devices/platform/gpio-keys/input/input0
hctosys: unable to open rtc device (rtc0)
Freeing unused kernel memory: 1024K
# Loading, please wait...
# Mounting filesystems...
# Check disk and init
### Press any key to stop and run shell... (2)print_req_error: I/O
error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock3, sector 0
mdadm: No arrays found in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
mvneta f1074000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver
[Marvell 88E1510]
mvneta f1074000.ethernet eth0: configuring for phy/rgmii-id link mode
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending discover...
mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.178.66...
Lease of 192.168.178.66 obtained, lease time 864000
Setting IP address 192.168.178.66 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending select for 192.168.178.66...
Lease of 192.168.178.66 obtained, lease time 864000
Setting IP address 192.168.178.66 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
/ # ls /dev/mtd*
/dev/mtd0 /dev/mtd2ro /dev/mtd5 /dev/mtdblock1 /dev/mtdblock6
/dev/mtd0ro /dev/mtd3 /dev/mtd5ro /dev/mtdblock2
/dev/mtd1 /dev/mtd3ro /dev/mtd6 /dev/mtdblock3
/dev/mtd1ro /dev/mtd4 /dev/mtd6ro /dev/mtdblock4
/dev/mtd2 /dev/mtd4ro /dev/mtdblock0 /dev/mtdblock5
------------- cherry-pick 90d617633368
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
Bad block table written to 0x00000ffe0000, version 0x01
Bad block table written to 0x00000ffc0000, version 0x01
7 ofpart partitions found on MTD device pxa3xx_nand-0
Creating 7 MTD partitions on "pxa3xx_nand-0":
0x000000000000-0x000000500000 : "u-Boot"
0x000000500000-0x000000a00000 : "uImage"
0x000000a00000-0x000000f00000 : "ramdisk"
0x000000f00000-0x00000d800000 : "image.cfs"
0x00000dd00000-0x00000ec00000 : "rescue firmware"
0x00000ec00000-0x000010000000 : "config"
0x00000d800000-0x00000dd00000 : "reserve"
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
libphy: Fixed MDIO Bus: probed
libphy: orion_mdio_bus: probed
mvneta f1074000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
usbcore: registered new interface driver lan78xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.usb: EHCI Host Controller
orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
ata1: SATA link down (SStatus 0 SControl F300)
orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.16.0+ ehci_hcd
usb usb1: SerialNumber: f1050000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
ata2: SATA link down (SStatus 0 SControl F300)
rtc-mv f1010300.rtc: internal RTC not ticking
i2c /dev entries driver
device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
marvell-cesa f1090000.crypto: CESA device successfully registered
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
Loading compiled-in X.509 certificates
armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
input: gpio-keys as /devices/platform/gpio-keys/input/input0
hctosys: unable to open rtc device (rtc0)
Freeing unused kernel memory: 1024K
# Loading, please wait...
# Mounting filesystems...
# Check disk and init
### Press any key to stop and run shell... (2)print_req_error: I/O
error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock3, sector 0
mdadm: No arrays found in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
mvneta f1074000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver
[Marvell 88E1510]
mvneta f1074000.ethernet eth0: configuring for phy/rgmii-id link mode
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending discover...
mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.178.70...
Lease of 192.168.178.70 obtained, lease time 864000
Setting IP address 192.168.178.70 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending select for 192.168.178.70...
Lease of 192.168.178.70 obtained, lease time 864000
Setting IP address 192.168.178.70 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
/ # ls /dev/mtd*
/dev/mtd0 /dev/mtd2ro /dev/mtd5 /dev/mtdblock1 /dev/mtdblock6
/dev/mtd0ro /dev/mtd3 /dev/mtd5ro /dev/mtdblock2
/dev/mtd1 /dev/mtd3ro /dev/mtd6 /dev/mtdblock3
/dev/mtd1ro /dev/mtd4 /dev/mtd6ro /dev/mtdblock4
/dev/mtd2 /dev/mtd4ro /dev/mtdblock0 /dev/mtdblock5
------------- cherry-pick 7fd130f7416f -X theirs
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
Bad block table written to 0x00000ffe0000, version 0x01
Bad block table written to 0x00000ffc0000, version 0x01
7 ofpart partitions found on MTD device pxa3xx_nand-0
Creating 7 MTD partitions on "pxa3xx_nand-0":
0x000000000000-0x000000500000 : "u-Boot"
0x000000500000-0x000000a00000 : "uImage"
0x000000a00000-0x000000f00000 : "ramdisk"
0x000000f00000-0x00000d800000 : "image.cfs"
0x00000dd00000-0x00000ec00000 : "rescue firmware"
0x00000ec00000-0x000010000000 : "config"
0x00000d800000-0x00000dd00000 : "reserve"
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
libphy: Fixed MDIO Bus: probed
libphy: orion_mdio_bus: probed
mvneta f1074000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
usbcore: registered new interface driver lan78xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.usb: EHCI Host Controller
orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
ata1: SATA link down (SStatus 0 SControl F300)
orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.16.0+ ehci_hcd
usb usb1: SerialNumber: f1050000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
ata2: SATA link down (SStatus 0 SControl F300)
rtc-mv f1010300.rtc: internal RTC not ticking
i2c /dev entries driver
device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
marvell-cesa f1090000.crypto: CESA device successfully registered
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
Loading compiled-in X.509 certificates
armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
input: gpio-keys as /devices/platform/gpio-keys/input/input0
hctosys: unable to open rtc device (rtc0)
Freeing unused kernel memory: 1024K
# Loading, please wait...
# Mounting filesystems...
# Check disk and init
### Press any key to stop and run shell... (2)print_req_error: I/O
error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock3, sector 0
mdadm: No arrays found in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
mvneta f1074000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver
[Marvell 88E1510]
mvneta f1074000.ethernet eth0: configuring for phy/rgmii-id link mode
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending discover...
mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.178.72...
Lease of 192.168.178.72 obtained, lease time 864000
Setting IP address 192.168.178.72 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending select for 192.168.178.72...
Lease of 192.168.178.72 obtained, lease time 864000
Setting IP address 192.168.178.72 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
/ # ls /dev/mtd*
/dev/mtd0 /dev/mtd2ro /dev/mtd5 /dev/mtdblock1 /dev/mtdblock6
/dev/mtd0ro /dev/mtd3 /dev/mtd5ro /dev/mtdblock2
/dev/mtd1 /dev/mtd3ro /dev/mtd6 /dev/mtdblock3
/dev/mtd1ro /dev/mtd4 /dev/mtd6ro /dev/mtdblock4
/dev/mtd2 /dev/mtd4ro /dev/mtdblock0 /dev/mtdblock5
------------- cherry-pick 53c83b59759c
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
Bad block table written to 0x00000ffe0000, version 0x01
Bad block table written to 0x00000ffc0000, version 0x01
7 ofpart partitions found on MTD device pxa3xx_nand-0
Creating 7 MTD partitions on "pxa3xx_nand-0":
0x000000000000-0x000000500000 : "u-Boot"
0x000000500000-0x000000a00000 : "uImage"
0x000000a00000-0x000000f00000 : "ramdisk"
0x000000f00000-0x00000d800000 : "image.cfs"
0x00000dd00000-0x00000ec00000 : "rescue firmware"
0x00000ec00000-0x000010000000 : "config"
0x00000d800000-0x00000dd00000 : "reserve"
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
libphy: Fixed MDIO Bus: probed
libphy: orion_mdio_bus: probed
mvneta f1074000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
usbcore: registered new interface driver lan78xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.usb: EHCI Host Controller
orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
ata1: SATA link down (SStatus 0 SControl F300)
orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.16.0+ ehci_hcd
usb usb1: SerialNumber: f1050000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
ata2: SATA link down (SStatus 0 SControl F300)
rtc-mv f1010300.rtc: internal RTC not ticking
i2c /dev entries driver
device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
marvell-cesa f1090000.crypto: CESA device successfully registered
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
Loading compiled-in X.509 certificates
armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
input: gpio-keys as /devices/platform/gpio-keys/input/input0
hctosys: unable to open rtc device (rtc0)
Freeing unused kernel memory: 1024K
# Loading, please wait...
# Mounting filesystems...
# Check disk and init
### Press any key to stop and run shell... (2)print_req_error: I/O
error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock3, sector 0
mdadm: No arrays found in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
mvneta f1074000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver
[Marvell 88E1510]
mvneta f1074000.ethernet eth0: configuring for phy/rgmii-id link mode
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending discover...
mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.178.73...
Lease of 192.168.178.73 obtained, lease time 864000
Setting IP address 192.168.178.73 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending select for 192.168.178.73...
Lease of 192.168.178.73 obtained, lease time 864000
Setting IP address 192.168.178.73 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
/ # ls /dev/mtd*
/dev/mtd0 /dev/mtd2ro /dev/mtd5 /dev/mtdblock1 /dev/mtdblock6
/dev/mtd0ro /dev/mtd3 /dev/mtd5ro /dev/mtdblock2
/dev/mtd1 /dev/mtd3ro /dev/mtd6 /dev/mtdblock3
/dev/mtd1ro /dev/mtd4 /dev/mtd6ro /dev/mtdblock4
/dev/mtd2 /dev/mtd4ro /dev/mtdblock0 /dev/mtdblock5
------------- cherry-pick cafb56dd741e
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
Bad block table written to 0x00000ffe0000, version 0x01
Bad block table written to 0x00000ffc0000, version 0x01
7 ofpart partitions found on MTD device pxa3xx_nand-0
Creating 7 MTD partitions on "pxa3xx_nand-0":
0x000000000000-0x000000500000 : "u-Boot"
0x000000500000-0x000000a00000 : "uImage"
0x000000a00000-0x000000f00000 : "ramdisk"
0x000000f00000-0x00000d800000 : "image.cfs"
0x00000dd00000-0x00000ec00000 : "rescue firmware"
0x00000ec00000-0x000010000000 : "config"
0x00000d800000-0x00000dd00000 : "reserve"
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
libphy: Fixed MDIO Bus: probed
libphy: orion_mdio_bus: probed
mvneta f1074000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
usbcore: registered new interface driver lan78xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.usb: EHCI Host Controller
orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
ata1: SATA link down (SStatus 0 SControl F300)
orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.16.0+ ehci_hcd
usb usb1: SerialNumber: f1050000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
ata2: SATA link down (SStatus 0 SControl F300)
rtc-mv f1010300.rtc: internal RTC not ticking
i2c /dev entries driver
device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
marvell-cesa f1090000.crypto: CESA device successfully registered
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
Loading compiled-in X.509 certificates
armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
input: gpio-keys as /devices/platform/gpio-keys/input/input0
hctosys: unable to open rtc device (rtc0)
Freeing unused kernel memory: 1024K
# Loading, please wait...
# Mounting filesystems...
# Check disk and init
### Press any key to stop and run shell... (2)print_req_error: I/O
error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock3, sector 0
mdadm: No arrays found in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
mvneta f1074000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver
[Marvell 88E1510]
mvneta f1074000.ethernet eth0: configuring for phy/rgmii-id link mode
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending discover...
mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.178.74...
Lease of 192.168.178.74 obtained, lease time 864000
Setting IP address 192.168.178.74 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending select for 192.168.178.74...
Lease of 192.168.178.74 obtained, lease time 864000
Setting IP address 192.168.178.74 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
/ # ls /dev/mtd*
/dev/mtd0 /dev/mtd2ro /dev/mtd5 /dev/mtdblock1 /dev/mtdblock6
/dev/mtd0ro /dev/mtd3 /dev/mtd5ro /dev/mtdblock2
/dev/mtd1 /dev/mtd3ro /dev/mtd6 /dev/mtdblock3
/dev/mtd1ro /dev/mtd4 /dev/mtd6ro /dev/mtdblock4
/dev/mtd2 /dev/mtd4ro /dev/mtdblock0 /dev/mtdblock5
------------- cherry-pick c27075772d1f
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
Bad block table written to 0x00000ffe0000, version 0x01
Bad block table written to 0x00000ffc0000, version 0x01
7 ofpart partitions found on MTD device pxa3xx_nand-0
Creating 7 MTD partitions on "pxa3xx_nand-0":
0x000000000000-0x000000500000 : "u-Boot"
0x000000500000-0x000000a00000 : "uImage"
0x000000a00000-0x000000f00000 : "ramdisk"
0x000000f00000-0x00000d800000 : "image.cfs"
0x00000dd00000-0x00000ec00000 : "rescue firmware"
0x00000ec00000-0x000010000000 : "config"
0x00000d800000-0x00000dd00000 : "reserve"
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
libphy: Fixed MDIO Bus: probed
libphy: orion_mdio_bus: probed
mvneta f1074000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
usbcore: registered new interface driver lan78xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.usb: EHCI Host Controller
orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
ata1: SATA link down (SStatus 0 SControl F300)
orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.16.0+ ehci_hcd
usb usb1: SerialNumber: f1050000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
ata2: SATA link down (SStatus 0 SControl F300)
rtc-mv f1010300.rtc: internal RTC not ticking
i2c /dev entries driver
device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
marvell-cesa f1090000.crypto: CESA device successfully registered
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
Loading compiled-in X.509 certificates
armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
input: gpio-keys as /devices/platform/gpio-keys/input/input0
hctosys: unable to open rtc device (rtc0)
Freeing unused kernel memory: 1024K
# Loading, please wait...
# Mounting filesystems...
# Check disk and init
### Press any key to stop and run shell... (2)print_req_error: I/O
error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock3, sector 0
mdadm: No arrays found in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
mvneta f1074000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver
[Marvell 88E1510]
mvneta f1074000.ethernet eth0: configuring for phy/rgmii-id link mode
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending discover...
mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.178.75...
Lease of 192.168.178.75 obtained, lease time 864000
Setting IP address 192.168.178.75 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending select for 192.168.178.75...
Lease of 192.168.178.75 obtained, lease time 864000
Setting IP address 192.168.178.75 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
/ # ls /dev/mtd*
/dev/mtd0 /dev/mtd2ro /dev/mtd5 /dev/mtdblock1 /dev/mtdblock6
/dev/mtd0ro /dev/mtd3 /dev/mtd5ro /dev/mtdblock2
/dev/mtd1 /dev/mtd3ro /dev/mtd6 /dev/mtdblock3
/dev/mtd1ro /dev/mtd4 /dev/mtd6ro /dev/mtdblock4
/dev/mtd2 /dev/mtd4ro /dev/mtdblock0 /dev/mtdblock5
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-14 17:16 ` David Schaefer
2020-12-14 21:24 ` Richard Weinberger
@ 2020-12-15 15:50 ` David Schaefer
2020-12-15 15:56 ` Miquel Raynal
1 sibling, 1 reply; 16+ messages in thread
From: David Schaefer @ 2020-12-15 15:50 UTC (permalink / raw)
To: Richard Weinberger; +Cc: linux-mtd, Miquel Raynal
Well, I now was brave enough to try to write to the block devices with
the last kernel and it failed, io error.
Kind regards
Am Mo., 14. Dez. 2020 um 18:16 Uhr schrieb David Schaefer
<david.tillmann.schaefer@gmail.com>:
>
> If this is a regression, how can we continue here? Can I give hardware
> specs and logs? I have soldered on the board to access UART. I can
> provide e.g. boot logs.
>
> /David
>
> Am Mo., 14. Dez. 2020 um 16:20 Uhr schrieb Richard Weinberger <richard@nod.at>:
> >
> > David,
> >
> > ----- Ursprüngliche Mail -----
> > > I have checked the kernel configuration. For 4.15.18 I have these settings:
> > > CONFIG_MTD_NAND_ECC=y
> > > CONFIG_MTD_NAND=y
> > > CONFIG_MTD_NAND_PXA3xx=y
> > >
> > > and for 4.16.1
> > >
> > > CONFIG_MTD_NAND_ECC=y
> > > CONFIG_MTD_NAND=y
> > > CONFIG_MTD_NAND_MARVELL=y
> > >
> > > I actually copied the working configuration from 4.15.18 to 4.16.1,
> > > did make oldconfig, and compiled it the same way as 4.15.18. Like I
> > > said above, 4.15 works, 4.16 does not.
> > > I hope this answers your question whether I see the issue with the new
> > > and the old marvell drivers because I am not 100% sure what you refer
> > > to here (I guess you mean PXA3XX vs NAND).
> >
> > Ah, right. I forgot that the old driver got removed. I thought we kept it for a few releases. ;-\
> > So there is a regression.
> >
> > Thanks,
> > //richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-15 15:50 ` David Schaefer
@ 2020-12-15 15:56 ` Miquel Raynal
2020-12-15 16:34 ` David Schaefer
0 siblings, 1 reply; 16+ messages in thread
From: Miquel Raynal @ 2020-12-15 15:56 UTC (permalink / raw)
To: David Schaefer; +Cc: Richard Weinberger, linux-mtd
Hi David,
David Schaefer <david.tillmann.schaefer@gmail.com> wrote on Tue, 15 Dec
2020 16:50:34 +0100:
> Well, I now was brave enough to try to write to the block devices with
> the last kernel and it failed, io error.
I saw successful logs in your previous e-mail. Was I misunderstanding
something?
Also there is absolutely nothing we can do without the logs (including
boot).
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-15 15:56 ` Miquel Raynal
@ 2020-12-15 16:34 ` David Schaefer
2020-12-15 16:46 ` Miquel Raynal
0 siblings, 1 reply; 16+ messages in thread
From: David Schaefer @ 2020-12-15 16:34 UTC (permalink / raw)
To: Miquel Raynal; +Cc: Richard Weinberger, linux-mtd
Hi Miquel,
Am Di., 15. Dez. 2020 um 16:56 Uhr schrieb Miquel Raynal
<miquel.raynal@bootlin.com>:
> > Well, I now was brave enough to try to write to the block devices with
> > the last kernel and it failed, io error.
>
> I saw successful logs in your previous e-mail. Was I misunderstanding
> something?
>
> Also there is absolutely nothing we can do without the logs (including
> boot).
In my last mail I sent 8 non-complete bootlogs from the region that
might be important as
I understand it. Starting with the second commit the system boots up
and the devices
appear but I have several different issues like
- marvell-nfc f10d0000.nand: Timeout waiting for RB signal
- armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
- hctosys: unable to open rtc device (rtc0)
- print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock3, sector 0
and dd reports
dd: writing '/dev/mtdblock1': Input/output error
I am not sure which of these messages above are due to the driver
issue. Also I would
like to be clear that eventually I would like to run a recent kernel,
I am running 4.16 only
for debugging the driver issue.
I have attached a complete bootlog for the kernel I obtained by
cherry-picking all the
commits (and solving conflicts with -X theirs) on the v4.16 tag.
Please advice me if I did
anything wrong or you need any more information.
Kind regards
David
Bootlog below:
BootROM 1.08
Booting from NAND flash
High speed PHY - Version: 2.1.2 (COM-PHY-V20)
Update PEX Device ID 0x67100
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver 4.5.0
DDR3 Training Sequence - Ended Successfully
Status = MV_OK
BootROM: Image checksum verification PASSED
** LOADER **
U-Boot 2011.12 (Dec 24 2013 - 20:21:45) Marvell version: v2011.12
2013_Q1.2 (ALPHA U-BOOT : 1.0)
Board: RD-88F6710_ALpha_KingsCanyon
SoC: MV6710 A1
CPU: Marvell PJ4B v7 UP (Rev 1) LE
CPU @ 1200 [MHz]
L2 @ 600 [MHz]
TClock @ 200 [MHz]
DDR @ 600 [MHz]
DDR 16Bit Width, FastPath Memory Access
DRAM: 512 MiB
Map: Code: 0x1fef5000:0x1ff9faac
BSS: 0x1ffef784
Stack: 0x1f9f4ef8
Heap: 0x1f9f5000:0x1fef5000
NAND: flash id : daad
256 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: Bad block at 0x00000e7c0000
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1): Detected No Link.
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Modules/Interfaces Detected:
RGMII1 Phy
PEX0 (Lane 0)
PEX1 (Lane 1)
SATA0 (Lane 2)
SATA1 (Lane 3)
Not Marvell PHY id1 ffff id2 ffff
Enable HD1
Enable HD2
Net: egiga1
Warning: egiga1 MAC addresses don't match:
Address in SROM is 00:50:43:02:00:00
Address in environment is 00:50:43:02:02:00
Hit any key to stop autoboot: 0
Marvell>> dhcp; setenv serverip 192.168.178.34; tftp 0x2000000
uImage416-patch8; tftp 0x3000000 uRamdisk; bootm 0x2000000 0x3000000
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 28
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 158
*** Unhandled DHCP Option in OFFER/ACK: 28
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 158
DHCP client bound to address 192.168.178.76
Using egiga1 device
TFTP from server 192.168.178.34; our IP address is 192.168.178.76
Filename 'uImage416-patch8'.
Load address: 0x2000000
Loading: #################################################################
#################################################################
#################################################################
########################################################
done
Bytes transferred = 3670168 (380098 hex)
Using egiga1 device
TFTP from server 192.168.178.34; our IP address is 192.168.178.76
Filename 'uRamdisk'.
Load address: 0x3000000
Loading: #################################################################
#################################################################
#####################################################
done
Bytes transferred = 2679866 (28e43a hex)
## Booting image at 02000000 ...
## Booting kernel from Legacy Image at 02000000 ...
Image Name: armada-370-wdmc-mirror-gen1
Created: 2020-12-15 9:54:58 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3670104 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
Image Name: Ramdisk
Created: 2017-02-04 18:43:13 UTC
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 2679802 Bytes = 2.6 MiB
Load Address: 00e00000
Entry Point: 00e00000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 4.16.0+ (david@debian) (gcc version 8.3.0 (Debian
8.3.0-2)) #4 SMP Tue Dec 15 03:44:21 EST 2020
CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
OF: fdt: Machine model: WD MyCloud Mirror
Memory policy: Data cache writeback
CPU: All CPU(s) started in SVC mode.
percpu: Embedded 15 pages/cpu @(ptrval) s32716 r8192 d20532 u61440
Built 1 zonelists, mobility grouping on. Total pages: 129920
Kernel command line: root=/dev/ram console=ttyS0,115200 max_loop=32
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 505736K/524288K available (7179K kernel code, 296K rwdata,
1804K rodata, 1024K init, 220K bss, 18552K reserved, 0K cma-reserved,
0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xe0800000 - 0xff800000 ( 496 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0x(ptrval) - 0x(ptrval) (8172 kB)
.init : 0x(ptrval) - 0x(ptrval) (1024 kB)
.data : 0x(ptrval) - 0x(ptrval) ( 296 kB)
.bss : 0x(ptrval) - 0x(ptrval) ( 221 kB)
Hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
L2C: DT/platform modifies aux control register: 0x12086302 -> 0x1a086302
Aurora cache controller enabled, 4 ways, 256 kB
Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302
Switching to timer-based delay loop, resolution 53ns
sched_clock: 32 bits at 18MHz, resolution 53ns, wraps every 114532461029ns
clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 101933890472 ns
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer
frequency.. 37.50 BogoMIPS (lpj=187500)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket -1, mpidr 0
Setting up static identity map for 0x100000 - 0x100060
mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1
mvebu-pmsu: Initializing Power Management Service Unit
Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
smp: Brought up 1 node, 1 CPU
SMP: Total of 1 processors activated (37.50 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
random: get_random_u32 called from bucket_table_alloc+0x7c/0x194 with
crng_init=0
VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff,
max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: 2, 16384 bytes)
xor: measuring software checksum speed
arm4regs : 1105.200 MB/sec
8regs : 868.800 MB/sec
32regs : 1043.200 MB/sec
xor: using function: arm4regs (1105.200 MB/sec)
pinctrl core: initialized pinctrl subsystem
random: fast init done
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cryptd: max_cpu_qlen set to 1000
raid6: int32x1 gen() 170 MB/s
raid6: int32x1 xor() 225 MB/s
raid6: int32x2 gen() 254 MB/s
raid6: int32x2 xor() 251 MB/s
raid6: int32x4 gen() 314 MB/s
raid6: int32x4 xor() 243 MB/s
raid6: int32x8 gen() 339 MB/s
raid6: int32x8 xor() 229 MB/s
raid6: using algorithm int32x8 gen() 339 MB/s
raid6: .... xor() 229 MB/s, rmw enabled
raid6: using intx1 recovery algorithm
reg-fixed-voltage regulators:regulator@1: could not find pctldev for
node /soc/internal-regs/pin-ctrl@18000/xhci-pwr-pin, deferring probe
reg-fixed-voltage regulators:regulator@2: could not find pctldev for
node /soc/internal-regs/pin-ctrl@18000/sata-1-pwr-pin, deferring probe
reg-fixed-voltage regulators:regulator@3: could not find pctldev for
node /soc/internal-regs/pin-ctrl@18000/sata-2-pwr-pin, deferring probe
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
<giometti@linux.it>
PTP clock support registered
Bluetooth: Core ver 2.22
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
clocksource: Switched to clocksource armada_370_xp_clocksource
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
FS-Cache: Loaded
CacheFiles: Loaded
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 2620K
Initialise system trusted keyrings
workingset: timestamp_bits=14 max_order=17 bucket_order=3
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
FS-Cache: Netfs 'cifs' registered for caching
async_tx: api initialized (async)
Key type asymmetric registered
Asymmetric key parser 'x509' registered
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
io scheduler kyber registered
armada-370-pinctrl f1018000.pin-ctrl: registered pinctrl driver
mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
PCI: bus0: Fast back to back transfers disabled
pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
PCI: bus1: Fast back to back transfers disabled
PCI: bus2: Fast back to back transfers enabled
pci 0000:00:01.0: BAR 8: assigned [mem 0xf8000000-0xf80fffff]
pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf8001fff 64bit]
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff]
pci 0000:00:02.0: PCI bridge to [bus 02]
mv_xor f1060800.xor: Marvell shared XOR driver
mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
mv_xor f1060900.xor: Marvell shared XOR driver
mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
console [ttyS0] disabled
f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 20, base_baud =
12500000) is a 16550A
console [ttyS0] enabled
f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 21, base_baud =
12500000) is a 16550A
brd: module loaded
loop: module loaded
sata_mv f10a0000.sata: slots 32 ports 2
scsi host0: sata_mv
scsi host1: sata_mv
ata1: SATA max UDMA/133 irq 29
ata2: SATA max UDMA/133 irq 29
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
Bad block table written to 0x00000ffe0000, version 0x01
Bad block table written to 0x00000ffc0000, version 0x01
7 ofpart partitions found on MTD device pxa3xx_nand-0
Creating 7 MTD partitions on "pxa3xx_nand-0":
0x000000000000-0x000000500000 : "u-Boot"
0x000000500000-0x000000a00000 : "uImage"
0x000000a00000-0x000000f00000 : "ramdisk"
0x000000f00000-0x00000d800000 : "image.cfs"
0x00000dd00000-0x00000ec00000 : "rescue firmware"
0x00000ec00000-0x000010000000 : "config"
0x00000d800000-0x00000dd00000 : "reserve"
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
libphy: Fixed MDIO Bus: probed
libphy: orion_mdio_bus: probed
mvneta f1074000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
usbcore: registered new interface driver lan78xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.usb: EHCI Host Controller
orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1050000.usb: irq 27, io mem 0xf1050000
ata1: SATA link down (SStatus 0 SControl F300)
orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.16.0+ ehci_hcd
usb usb1: SerialNumber: f1050000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
ata2: SATA link down (SStatus 0 SControl F300)
rtc-mv f1010300.rtc: internal RTC not ticking
i2c /dev entries driver
device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
marvell-cesa f1090000.crypto: CESA device successfully registered
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
Loading compiled-in X.509 certificates
armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
input: gpio-keys as /devices/platform/gpio-keys/input/input0
hctosys: unable to open rtc device (rtc0)
Freeing unused kernel memory: 1024K
# Loading, please wait...
# Mounting filesystems...
# Check disk and init
### Press any key to stop and run shell... (2)print_req_error: I/O
error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock6, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock5, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock4, sector 0
print_req_error: I/O error, dev mtdblock3, sector 0
mdadm: No arrays found in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
mvneta f1074000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver
[Marvell 88E1510]
mvneta f1074000.ethernet eth0: configuring for phy/rgmii-id link mode
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending discover...
mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.178.78...
Lease of 192.168.178.78 obtained, lease time 864000
Setting IP address 192.168.178.78 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending select for 192.168.178.78...
Lease of 192.168.178.78 obtained, lease time 864000
Setting IP address 192.168.178.78 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
/ # ls /dev/mtd
mtd0 mtd1ro mtd3 mtd4ro mtd6 mtdblock1 mtdblock4
mtd0ro mtd2 mtd3ro mtd5 mtd6ro mtdblock2 mtdblock5
mtd1 mtd2ro mtd4 mtd5ro mtdblock0 mtdblock3 mtdblock6
/ # ls /dev/mtdblock*
/dev/mtdblock0 /dev/mtdblock2 /dev/mtdblock4 /dev/mtdblock6
/dev/mtdblock1 /dev/mtdblock3 /dev/mtdblock5
/ # dd if=/dev/zero of=/dev/mtdblock1
print_req_error: 9 callbacks suppressed
print_req_error: I/O error, dev mtdblock1, sector 0
dd: writing '/dev/mtdblock1': Input/output error
1+0 records in
0+0 records out
0 bytes (0B) copied, 0.009045 seconds, 0B/s
/ #
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-15 16:34 ` David Schaefer
@ 2020-12-15 16:46 ` Miquel Raynal
2020-12-15 21:20 ` David Schaefer
0 siblings, 1 reply; 16+ messages in thread
From: Miquel Raynal @ 2020-12-15 16:46 UTC (permalink / raw)
To: David Schaefer; +Cc: Richard Weinberger, linux-mtd
Hi David,
David Schaefer <david.tillmann.schaefer@gmail.com> wrote on Tue, 15 Dec
2020 17:34:45 +0100:
> Hi Miquel,
> Am Di., 15. Dez. 2020 um 16:56 Uhr schrieb Miquel Raynal
> <miquel.raynal@bootlin.com>:
> > > Well, I now was brave enough to try to write to the block devices with
> > > the last kernel and it failed, io error.
> >
> > I saw successful logs in your previous e-mail. Was I misunderstanding
> > something?
> >
> > Also there is absolutely nothing we can do without the logs (including
> > boot).
>
> In my last mail I sent 8 non-complete bootlogs from the region that
> might be important as
> I understand it. Starting with the second commit the system boots up
> and the devices
> appear but I have several different issues like
> - marvell-nfc f10d0000.nand: Timeout waiting for RB signal
This one is a real error but got fixed by another commit.
> - armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
> pinctrl core: failed to register map default (0): invalid type given
> reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
> - hctosys: unable to open rtc device (rtc0)
These are completely unrelated.
> - print_req_error: I/O error, dev mtdblock6, sector 0
> print_req_error: I/O error, dev mtdblock6, sector 0
> print_req_error: I/O error, dev mtdblock6, sector 0
> print_req_error: I/O error, dev mtdblock5, sector 0
> print_req_error: I/O error, dev mtdblock5, sector 0
> print_req_error: I/O error, dev mtdblock5, sector 0
> print_req_error: I/O error, dev mtdblock4, sector 0
> print_req_error: I/O error, dev mtdblock4, sector 0
> print_req_error: I/O error, dev mtdblock4, sector 0
> print_req_error: I/O error, dev mtdblock3, sector 0
This one seem related but I don't know from where it comes.
>
> and dd reports
>
> dd: writing '/dev/mtdblock1': Input/output error
Maybe I should ask you why you are using mtdblock and using dd on top
of it? If you want to tackle a NAND issue, you should probably address
the mtd device directly and use the tools provided by the mtd-utils
userspace test suite (nandpagetest seems a good fit).
Be careful these are destructive tests. Anyway you perhaps already lost
the content of your device (at least you lost the BBT).
> I am not sure which of these messages above are due to the driver
> issue. Also I would
> like to be clear that eventually I would like to run a recent kernel,
You might want to try a much more recent kernel then. Probably that
using a 5.9 or 5.10 is a good target for now.
> I am running 4.16 only
> for debugging the driver issue.
>
> I have attached a complete bootlog for the kernel I obtained by
> cherry-picking all the
> commits (and solving conflicts with -X theirs) on the v4.16 tag.
I really don't think using -X theirs blindly is wise, you should
definitely try to understand the conflict and merge it by hand.
> Please advice me if I did
> anything wrong or you need any more information.
>
Good luck :)
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-15 16:46 ` Miquel Raynal
@ 2020-12-15 21:20 ` David Schaefer
2020-12-15 22:04 ` David Schaefer
0 siblings, 1 reply; 16+ messages in thread
From: David Schaefer @ 2020-12-15 21:20 UTC (permalink / raw)
To: Miquel Raynal; +Cc: Richard Weinberger, linux-mtd
Hi Miquèl
> Maybe I should ask you why you are using mtdblock and using dd on top
> of it? If you want to tackle a NAND issue, you should probably address
> the mtd device directly and use the tools provided by the mtd-utils
> userspace test suite (nandpagetest seems a good fit).
What I am trying to accomplish is running a debian with a kernel more
than 4.15 on a WD MyCloud Ex2. I follow a written down approach that
has been led to success by others. It involves
dd if=/dev/zero of=/dev/mtdblock1
dd if=uImage of=/dev/mtdblock1
dd if=/dev/zero of=/dev/mtdblock2
dd if=uRamdisk of=/dev/mtdblock2
I could use more appropriate ways to deal with these devices if I knew of any.
> You might want to try a much more recent kernel then. Probably that
> using a 5.9 or 5.10 is a good target for now.
I am compiling 5.10 right now and am looking forward to the results. I
have had 5.4 running already with no mtdblock devices showing up.
> I really don't think using -X theirs blindly is wise, you should
> definitely try to understand the conflict and merge it by hand.
I tried but didn't feel to be in the position to make the call.
Anyhow, since I have seen the commits are all part of kernels 4.17,
4.20, 5.0, and 5.10 this will not be an issue now when I run 5.10.
> > - marvell-nfc f10d0000.nand: Timeout waiting for RB signal
> This one is a real error but got fixed by another commit.
> > - print_req_error: I/O error, dev mtdblock6, sector 0
> > print_req_error: I/O error, dev mtdblock6, sector 0
> > print_req_error: I/O error, dev mtdblock6, sector 0
> > print_req_error: I/O error, dev mtdblock5, sector 0
> > print_req_error: I/O error, dev mtdblock5, sector 0
> > print_req_error: I/O error, dev mtdblock5, sector 0
> > print_req_error: I/O error, dev mtdblock4, sector 0
> > print_req_error: I/O error, dev mtdblock4, sector 0
> > print_req_error: I/O error, dev mtdblock4, sector 0
> > print_req_error: I/O error, dev mtdblock3, sector 0
> This one seem related but I don't know from where it comes.
> > dd: writing '/dev/mtdblock1': Input/output error
I will check if I see these issues with 5.10 when it's built.
> > Please advise me if I did
> > anything wrong or you need any more information.
> Good luck :)
Thanks :)
Kind regards
David
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-15 21:20 ` David Schaefer
@ 2020-12-15 22:04 ` David Schaefer
2020-12-16 7:51 ` Miquel Raynal
0 siblings, 1 reply; 16+ messages in thread
From: David Schaefer @ 2020-12-15 22:04 UTC (permalink / raw)
To: Miquel Raynal; +Cc: Richard Weinberger, linux-mtd
Hi Miquel,
Am Di., 15. Dez. 2020 um 22:20 Uhr schrieb David Schaefer
<david.tillmann.schaefer@gmail.com>:
>
> Hi Miquèl
>
> > Maybe I should ask you why you are using mtdblock and using dd on top
> > of it? If you want to tackle a NAND issue, you should probably address
> > the mtd device directly and use the tools provided by the mtd-utils
> > userspace test suite (nandpagetest seems a good fit).
> What I am trying to accomplish is running a debian with a kernel more
> than 4.15 on a WD MyCloud Ex2. I follow a written down approach that
> has been led to success by others. It involves
> dd if=/dev/zero of=/dev/mtdblock1
> dd if=uImage of=/dev/mtdblock1
> dd if=/dev/zero of=/dev/mtdblock2
> dd if=uRamdisk of=/dev/mtdblock2
>
> I could use more appropriate ways to deal with these devices if I knew of any.
>
> > You might want to try a much more recent kernel then. Probably that
> > using a 5.9 or 5.10 is a good target for now.
> I am compiling 5.10 right now and am looking forward to the results. I
> have had 5.4 running already with no mtdblock devices showing up.
>
> > I really don't think using -X theirs blindly is wise, you should
> > definitely try to understand the conflict and merge it by hand.
> I tried but didn't feel to be in the position to make the call.
> Anyhow, since I have seen the commits are all part of kernels 4.17,
> 4.20, 5.0, and 5.10 this will not be an issue now when I run 5.10.
>
> > > - marvell-nfc f10d0000.nand: Timeout waiting for RB signal
> > This one is a real error but got fixed by another commit.
> > > - print_req_error: I/O error, dev mtdblock6, sector 0
> > > print_req_error: I/O error, dev mtdblock6, sector 0
> > > print_req_error: I/O error, dev mtdblock6, sector 0
> > > print_req_error: I/O error, dev mtdblock5, sector 0
> > > print_req_error: I/O error, dev mtdblock5, sector 0
> > > print_req_error: I/O error, dev mtdblock5, sector 0
> > > print_req_error: I/O error, dev mtdblock4, sector 0
> > > print_req_error: I/O error, dev mtdblock4, sector 0
> > > print_req_error: I/O error, dev mtdblock4, sector 0
> > > print_req_error: I/O error, dev mtdblock3, sector 0
> > This one seem related but I don't know from where it comes.
> > > dd: writing '/dev/mtdblock1': Input/output error
> I will check if I see these issues with 5.10 when it's built.
running 5.10 does not show any /dev/mtdblock devices. There are errors
in the boot showing up as
marvell-nfc soc:internal-regs:nand@d0000: invalid resource
marvell-nfc: probe of soc:internal-regs:nand@d0000 failed with error -22
What I am missing in the bootlog of kernel 5.10 is what I saw after
applying all 8 commits to 4.16, namely:
nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
nand: Hynix H27U2G8F2CTR-BC
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad eraseblock 1854 at 0x00000e7c0000
Bad block table written to 0x00000ffe0000, version 0x01
Bad block table written to 0x00000ffc0000, version 0x01
7 ofpart partitions found on MTD device pxa3xx_nand-0
Creating 7 MTD partitions on "pxa3xx_nand-0":
0x000000000000-0x000000500000 : "u-Boot"
0x000000500000-0x000000a00000 : "uImage"
0x000000a00000-0x000000f00000 : "ramdisk"
0x000000f00000-0x00000d800000 : "image.cfs"
0x00000dd00000-0x00000ec00000 : "rescue firmware"
0x00000ec00000-0x000010000000 : "config"
0x00000d800000-0x00000dd00000 : "reserve"
I have attached the complete bootlog here:
** LOADER **
U-Boot 2011.12 (Dec 24 2013 - 20:21:45) Marvell version: v2011.12
2013_Q1.2 (ALPHA U-BOOT : 1.0)
Board: RD-88F6710_ALpha_KingsCanyon
SoC: MV6710 A1
CPU: Marvell PJ4B v7 UP (Rev 1) LE
CPU @ 1200 [MHz]
L2 @ 600 [MHz]
TClock @ 200 [MHz]
DDR @ 600 [MHz]
DDR 16Bit Width, FastPath Memory Access
DRAM: 512 MiB
Map: Code: 0x1fef5000:0x1ff9faac
BSS: 0x1ffef784
Stack: 0x1f9f4ef8
Heap: 0x1f9f5000:0x1fef5000
NAND: flash id : daad
256 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: Bad block at 0x00000e7c0000
PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1): Detected No Link.
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Modules/Interfaces Detected:
RGMII1 Phy
PEX0 (Lane 0)
PEX1 (Lane 1)
SATA0 (Lane 2)
SATA1 (Lane 3)
Not Marvell PHY id1 ffff id2 ffff
Enable HD1
Enable HD2
Net: egiga1
Warning: egiga1 MAC addresses don't match:
Address in SROM is 00:50:43:02:00:00
Address in environment is 00:50:43:02:02:00
Hit any key to stop autoboot: 0
Marvell>> dhcp; setenv serverip 192.168.178.34; tftp 0x2000000
uImage510-5; tftp 0x3000000 uRamdisk; bootm 0x2000000 0x3000000
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 28
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 158
*** Unhandled DHCP Option in OFFER/ACK: 28
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 158
DHCP client bound to address 192.168.178.83
Using egiga1 device
TFTP from server 192.168.178.34; our IP address is 192.168.178.83
Filename 'uImage510-5'.
Load address: 0x2000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
############################################
done
Bytes transferred = 4458685 (4408bd hex)
Using egiga1 device
TFTP from server 192.168.178.34; our IP address is 192.168.178.83
Filename 'uRamdisk'.
Load address: 0x3000000
Loading: #################################################################
#################################################################
#####################################################
done
Bytes transferred = 2679866 (28e43a hex)
## Booting image at 02000000 ...
## Booting kernel from Legacy Image at 02000000 ...
Image Name: armada-370-wdmc-mirror-gen1
Created: 2020-12-15 21:56:29 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4458621 Bytes = 4.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
Image Name: Ramdisk
Created: 2017-02-04 18:43:13 UTC
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 2679802 Bytes = 2.6 MiB
Load Address: 00e00000
Entry Point: 00e00000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
DTB:0x00444E30 (0x00003A4D)
C:0x000080C0-0x00448920->0x00E7E400-0x012BEC60
DTB:0x012BB170 (0x00003AD6)
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 5.10.0 (david@debian) (arm-linux-gnueabi-gcc (Debian
8.3.0-2) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #5 SMP Tue
Dec 15 16:55:38 EST 2020
CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
OF: fdt: Machine model: WD MyCloud Mirror
Memory policy: Data cache writeback
Zone ranges:
Normal [mem 0x0000000000000000-0x000000001fffffff]
HighMem empty
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x0000000000000000-0x000000001fffffff]
Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
CPU: All CPU(s) started in SVC mode.
percpu: Embedded 15 pages/cpu s30028 r8192 d23220 u61440
Built 1 zonelists, mobility grouping on. Total pages: 129920
Kernel command line: root=/dev/ram console=ttyS0,115200 max_loop=32
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
mem auto-init: stack:off, heap alloc:off, heap free:off
Memory: 502320K/524288K available (9066K kernel code, 502K rwdata,
2120K rodata, 1024K init, 364K bss, 21968K reserved, 0K cma-reserved,
0K highmem)
rcu: Hierarchical RCU implementation.
rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
L2C: DT/platform modifies aux control register: 0x12086302 -> 0x1a086302
Aurora cache controller enabled, 4 ways, 256 kB
Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302
random: get_random_bytes called from start_kernel+0x324/0x4d0 with crng_init=0
Switching to timer-based delay loop, resolution 53ns
sched_clock: 32 bits at 18MHz, resolution 53ns, wraps every 114532461029ns
clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 101933890472 ns
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer
frequency.. 37.50 BogoMIPS (lpj=187500)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket -1, mpidr 0
Setting up static identity map for 0x100000 - 0x100060
mvebu-soc-id: MVEBU SoC ID=0x6710, Rev=0x1
mvebu-pmsu: Initializing Power Management Service Unit
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
smp: Brought up 1 node, 1 CPU
SMP: Total of 1 processors activated (37.50 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff,
max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: 2, 16384 bytes, linear)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
thermal_sys: Registered thermal governor 'step_wise'
cpuidle: using governor ladder
cryptd: max_cpu_qlen set to 1000
raid6: int32x8 gen() 422 MB/s
raid6: int32x8 xor() 264 MB/s
raid6: int32x4 gen() 477 MB/s
raid6: int32x4 xor() 270 MB/s
raid6: int32x2 gen() 526 MB/s
raid6: int32x2 xor() 255 MB/s
raid6: int32x1 gen() 497 MB/s
raid6: int32x1 xor() 217 MB/s
raid6: using algorithm int32x2 gen() 526 MB/s
raid6: .... xor() 255 MB/s, rmw enabled
raid6: using intx1 recovery algorithm
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
<giometti@linux.it>
PTP clock support registered
Bluetooth: Core ver 2.22
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
clocksource: Switched to clocksource armada_370_xp_clocksource
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
FS-Cache: Loaded
CacheFiles: Loaded
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 2620K
Initialise system trusted keyrings
workingset: timestamp_bits=14 max_order=17 bucket_order=3
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
FS-Cache: Netfs 'cifs' registered for caching
Key type cifs.idmap registered
xor: measuring software checksum speed
arm4regs : 1151 MB/sec
8regs : 901 MB/sec
32regs : 1085 MB/sec
xor: using function: arm4regs (1151 MB/sec)
async_tx: api initialized (async)
Key type asymmetric registered
Asymmetric key parser 'x509' registered
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
io scheduler kyber registered
armada-370-pinctrl f1018000.pin-ctrl: registered pinctrl driver
mvebu-pcie soc:pcie@82000000: host bridge /soc/pcie@82000000 ranges:
mvebu-pcie soc:pcie@82000000: MEM 0x00f1040000..0x00f1041fff ->
0x0000040000
mvebu-pcie soc:pcie@82000000: MEM 0x00f1080000..0x00f1081fff ->
0x0000080000
mvebu-pcie soc:pcie@82000000: MEM
0xffffffffffffffff..0x00fffffffe -> 0x0100000000
mvebu-pcie soc:pcie@82000000: IO
0xffffffffffffffff..0x00fffffffe -> 0x0100000000
mvebu-pcie soc:pcie@82000000: MEM
0xffffffffffffffff..0x00fffffffe -> 0x0200000000
mvebu-pcie soc:pcie@82000000: IO
0xffffffffffffffff..0x00fffffffe -> 0x0200000000
mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus
address [0x00040000-0x00041fff])
pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus
address [0x00080000-0x00081fff])
pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
pci 0000:00:01.0: [11ab:6710] type 01 class 0x060400
pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
pci 0000:00:02.0: [11ab:6710] type 01 class 0x060400
pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
PCI: bus0: Fast back to back transfers disabled
pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:01:00.0: [1912:0015] type 00 class 0x0c0330
pci 0000:01:00.0: reg 0x10: [mem 0x40000000-0x40001fff 64bit]
pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
PCI: bus1: Fast back to back transfers disabled
pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
PCI: bus2: Fast back to back transfers enabled
pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
pci 0000:00:01.0: BAR 8: assigned [mem 0xf8000000-0xf80fffff]
pci 0000:00:01.0: BAR 6: assigned [mem 0xf8100000-0xf81007ff pref]
pci 0000:00:02.0: BAR 6: assigned [mem 0xf8200000-0xf82007ff pref]
pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf8001fff 64bit]
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff]
pci 0000:00:02.0: PCI bridge to [bus 02]
mv_xor f1060800.xor: Marvell shared XOR driver
mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
mv_xor f1060900.xor: Marvell shared XOR driver
mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
printk: console [ttyS0] disabled
f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 28, base_baud =
12500000) is a 16550A
printk: console [ttyS0] enabled
f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 29, base_baud =
12500000) is a 16550A
brd: module loaded
loop: module loaded
sata_mv f10a0000.sata: slots 32 ports 2
scsi host0: sata_mv
scsi host1: sata_mv
ata1: SATA max UDMA/133 irq 37
ata2: SATA max UDMA/133 irq 37
marvell-nfc soc:internal-regs:nand@d0000: invalid resource
marvell-nfc: probe of soc:internal-regs:nand@d0000 failed with error -22
libphy: Fixed MDIO Bus: probed
libphy: orion_mdio_bus: probed
mvneta f1074000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
usbcore: registered new interface driver lan78xx
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.usb: EHCI Host Controller
orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1050000.usb: irq 35, io mem 0xf1050000
orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 5.10.0 ehci_hcd
usb usb1: SerialNumber: f1050000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
ata1: SATA link down (SStatus 0 SControl F300)
ata2: SATA link down (SStatus 0 SControl F300)
rtc-mv f1010300.rtc: internal RTC not ticking
i2c /dev entries driver
device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
marvell-cesa f1090000.crypto: CESA device successfully registered
hid: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
Loading compiled-in X.509 certificates
Key type ._fscrypt registered
Key type .fscrypt registered
Key type fscrypt-provisioning registered
armada-370-pinctrl f1018000.pin-ctrl: unsupported function gpio on pin mpp54
pinctrl core: failed to register map default (0): invalid type given
reg-fixed-voltage: probe of regulators:regulator@2 failed with error -22
input: gpio-keys as /devices/platform/gpio-keys/input/input0
Freeing unused kernel memory: 1024K
Run /init as init process
# Loading, please wait...
# Mounting filesystems...
# Check disk and init
### Press any key to stop and run shell... (2)mdadm: No arrays found
in config file or automatically
# /dev/md1 not exist!
# Runing a shell...
mvneta f1074000.ethernet eth0: PHY [f1072004.mdio-mii:00] driver
[Marvell 88E1510] (irq=POLL)
mvneta f1074000.ethernet eth0: configuring for phy/rgmii-id link mode
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
^[^[OR^[ORSending discover...
mvneta f1074000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.178.84...
Lease of 192.168.178.84 obtained, lease time 864000
Setting IP address 192.168.178.84 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
udhcpc (v1.24.1) started
Setting IP address 0.0.0.0 on eth0
Sending discover...
Sending select for 192.168.178.84...
Lease of 192.168.178.84 obtained, lease time 864000
Setting IP address 192.168.178.84 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.178.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.178.1
Do you have any idea?
Kind regards
David
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-15 22:04 ` David Schaefer
@ 2020-12-16 7:51 ` Miquel Raynal
2020-12-17 20:15 ` David Schaefer
0 siblings, 1 reply; 16+ messages in thread
From: Miquel Raynal @ 2020-12-16 7:51 UTC (permalink / raw)
To: David Schaefer; +Cc: Richard Weinberger, linux-mtd
Hi David,
David Schaefer <david.tillmann.schaefer@gmail.com> wrote on Tue, 15 Dec
2020 23:04:24 +0100:
> Hi Miquel,
>
> Am Di., 15. Dez. 2020 um 22:20 Uhr schrieb David Schaefer
> <david.tillmann.schaefer@gmail.com>:
> >
> > Hi Miquèl
> >
> > > Maybe I should ask you why you are using mtdblock and using dd on top
> > > of it? If you want to tackle a NAND issue, you should probably address
> > > the mtd device directly and use the tools provided by the mtd-utils
> > > userspace test suite (nandpagetest seems a good fit).
> > What I am trying to accomplish is running a debian with a kernel more
> > than 4.15 on a WD MyCloud Ex2. I follow a written down approach that
> > has been led to success by others. It involves
> > dd if=/dev/zero of=/dev/mtdblock1
> > dd if=uImage of=/dev/mtdblock1
> > dd if=/dev/zero of=/dev/mtdblock2
> > dd if=uRamdisk of=/dev/mtdblock2
> >
> > I could use more appropriate ways to deal with these devices if I knew of any.
> >
> > > You might want to try a much more recent kernel then. Probably that
> > > using a 5.9 or 5.10 is a good target for now.
> > I am compiling 5.10 right now and am looking forward to the results. I
> > have had 5.4 running already with no mtdblock devices showing up.
> >
> > > I really don't think using -X theirs blindly is wise, you should
> > > definitely try to understand the conflict and merge it by hand.
> > I tried but didn't feel to be in the position to make the call.
> > Anyhow, since I have seen the commits are all part of kernels 4.17,
> > 4.20, 5.0, and 5.10 this will not be an issue now when I run 5.10.
> >
> > > > - marvell-nfc f10d0000.nand: Timeout waiting for RB signal
> > > This one is a real error but got fixed by another commit.
> > > > - print_req_error: I/O error, dev mtdblock6, sector 0
> > > > print_req_error: I/O error, dev mtdblock6, sector 0
> > > > print_req_error: I/O error, dev mtdblock6, sector 0
> > > > print_req_error: I/O error, dev mtdblock5, sector 0
> > > > print_req_error: I/O error, dev mtdblock5, sector 0
> > > > print_req_error: I/O error, dev mtdblock5, sector 0
> > > > print_req_error: I/O error, dev mtdblock4, sector 0
> > > > print_req_error: I/O error, dev mtdblock4, sector 0
> > > > print_req_error: I/O error, dev mtdblock4, sector 0
> > > > print_req_error: I/O error, dev mtdblock3, sector 0
> > > This one seem related but I don't know from where it comes.
> > > > dd: writing '/dev/mtdblock1': Input/output error
> > I will check if I see these issues with 5.10 when it's built.
>
> running 5.10 does not show any /dev/mtdblock devices. There are errors
> in the boot showing up as
> marvell-nfc soc:internal-regs:nand@d0000: invalid resource
> marvell-nfc: probe of soc:internal-regs:nand@d0000 failed with error -22
Perhaps the issues comes from your device tree, as this lines says. You
should check the bindings and verify they are in sync.
Bindings should be backward compatible but who knows...
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
2020-12-16 7:51 ` Miquel Raynal
@ 2020-12-17 20:15 ` David Schaefer
0 siblings, 0 replies; 16+ messages in thread
From: David Schaefer @ 2020-12-17 20:15 UTC (permalink / raw)
To: Miquel Raynal; +Cc: Richard Weinberger, linux-mtd
Hi Miquel and Richard
Thanks for all the help and support. I might be looking into this pet
project in the future and appreciate the conversation we had. Stay
safe!
Kind regards
David
Am Mi., 16. Dez. 2020 um 08:51 Uhr schrieb Miquel Raynal
<miquel.raynal@bootlin.com>:
>
> Hi David,
>
> David Schaefer <david.tillmann.schaefer@gmail.com> wrote on Tue, 15 Dec
> 2020 23:04:24 +0100:
>
> > Hi Miquel,
> >
> > Am Di., 15. Dez. 2020 um 22:20 Uhr schrieb David Schaefer
> > <david.tillmann.schaefer@gmail.com>:
> > >
> > > Hi Miquèl
> > >
> > > > Maybe I should ask you why you are using mtdblock and using dd on top
> > > > of it? If you want to tackle a NAND issue, you should probably address
> > > > the mtd device directly and use the tools provided by the mtd-utils
> > > > userspace test suite (nandpagetest seems a good fit).
> > > What I am trying to accomplish is running a debian with a kernel more
> > > than 4.15 on a WD MyCloud Ex2. I follow a written down approach that
> > > has been led to success by others. It involves
> > > dd if=/dev/zero of=/dev/mtdblock1
> > > dd if=uImage of=/dev/mtdblock1
> > > dd if=/dev/zero of=/dev/mtdblock2
> > > dd if=uRamdisk of=/dev/mtdblock2
> > >
> > > I could use more appropriate ways to deal with these devices if I knew of any.
> > >
> > > > You might want to try a much more recent kernel then. Probably that
> > > > using a 5.9 or 5.10 is a good target for now.
> > > I am compiling 5.10 right now and am looking forward to the results. I
> > > have had 5.4 running already with no mtdblock devices showing up.
> > >
> > > > I really don't think using -X theirs blindly is wise, you should
> > > > definitely try to understand the conflict and merge it by hand.
> > > I tried but didn't feel to be in the position to make the call.
> > > Anyhow, since I have seen the commits are all part of kernels 4.17,
> > > 4.20, 5.0, and 5.10 this will not be an issue now when I run 5.10.
> > >
> > > > > - marvell-nfc f10d0000.nand: Timeout waiting for RB signal
> > > > This one is a real error but got fixed by another commit.
> > > > > - print_req_error: I/O error, dev mtdblock6, sector 0
> > > > > print_req_error: I/O error, dev mtdblock6, sector 0
> > > > > print_req_error: I/O error, dev mtdblock6, sector 0
> > > > > print_req_error: I/O error, dev mtdblock5, sector 0
> > > > > print_req_error: I/O error, dev mtdblock5, sector 0
> > > > > print_req_error: I/O error, dev mtdblock5, sector 0
> > > > > print_req_error: I/O error, dev mtdblock4, sector 0
> > > > > print_req_error: I/O error, dev mtdblock4, sector 0
> > > > > print_req_error: I/O error, dev mtdblock4, sector 0
> > > > > print_req_error: I/O error, dev mtdblock3, sector 0
> > > > This one seem related but I don't know from where it comes.
> > > > > dd: writing '/dev/mtdblock1': Input/output error
> > > I will check if I see these issues with 5.10 when it's built.
> >
> > running 5.10 does not show any /dev/mtdblock devices. There are errors
> > in the boot showing up as
> > marvell-nfc soc:internal-regs:nand@d0000: invalid resource
> > marvell-nfc: probe of soc:internal-regs:nand@d0000 failed with error -22
>
> Perhaps the issues comes from your device tree, as this lines says. You
> should check the bindings and verify they are in sync.
>
> Bindings should be backward compatible but who knows...
>
> Thanks,
> Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2020-12-17 20:16 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-14 8:03 WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc David Schaefer
2020-12-14 13:36 ` Richard Weinberger
2020-12-14 14:58 ` David Schaefer
2020-12-14 15:20 ` Richard Weinberger
2020-12-14 17:16 ` David Schaefer
2020-12-14 21:24 ` Richard Weinberger
2020-12-14 23:03 ` Miquel Raynal
2020-12-15 10:14 ` David Schaefer
2020-12-15 15:50 ` David Schaefer
2020-12-15 15:56 ` Miquel Raynal
2020-12-15 16:34 ` David Schaefer
2020-12-15 16:46 ` Miquel Raynal
2020-12-15 21:20 ` David Schaefer
2020-12-15 22:04 ` David Schaefer
2020-12-16 7:51 ` Miquel Raynal
2020-12-17 20:15 ` David Schaefer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.