Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-04-18 Thread José Vázquez
2014-04-07 22:19 GMT+02:00, Jonas Gorski : > On Mon, Apr 7, 2014 at 10:11 PM, José Vázquez > wrote: >> The initial tests point that there is no data corruption in jffs2. Good >> catch! >> There are still some strange messages but maybe are due to the high >> amount of debug info and the jffs2 file

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-04-07 Thread Jonas Gorski
On Mon, Apr 7, 2014 at 10:11 PM, José Vázquez wrote: > The initial tests point that there is no data corruption in jffs2. Good catch! > There are still some strange messages but maybe are due to the high > amount of debug info and the jffs2 filesystem works fine: > > [ 18.584000] [ c

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-04-07 Thread José Vázquez
The initial tests point that there is no data corruption in jffs2. Good catch! There are still some strange messages but maybe are due to the high amount of debug info and the jffs2 filesystem works fine: [ 18.584000] [ cut here ] r overlay mount [ 18.584000] WARNING: a

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-04-07 Thread José Vázquez
If it worked for you surely surely will work for the other 6368. We will send the feedback soon. Thanks in advance: Pepe 2014-04-07 0:09 GMT+02:00, Jonas Gorski : > On Sat, Feb 1, 2014 at 1:06 PM, Álvaro Fernández Rojas > wrote: >> AFAIK anyone with a Neufbox 6 should be able to test if the pro

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-04-06 Thread Jonas Gorski
On Sat, Feb 1, 2014 at 1:06 PM, Álvaro Fernández Rojas wrote: > AFAIK anyone with a Neufbox 6 should be able to test if the problem happens > on SMP + SPI flash. > > I don't have any SMP + SPI flash brcm63xx device that is currently supported > by OpenWrt. > When Florian releases the BCM3380 pat

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-02-01 Thread Álvaro Fernández Rojas
AFAIK anyone with a Neufbox 6 should be able to test if the problem happens on SMP + SPI flash. I don't have any SMP + SPI flash brcm63xx device that is currently supported by OpenWrt. When Florian releases the BCM3380 patches I'll be able to test this with my Netgear CG3100Dv3. Regards, Álvar

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-02-01 Thread José Vázquez
> > I'm pretty sure that the jffs2 file name corruption problem doesn't > happen BCM63xx SoCs with spi flash and smp enabled, so, if this is > correct, seems to be a race condition between the flash type, jffs2 > and some Broadcom SoCs, as Jonas pointed some time ago. Can somebody confirm is the pr

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-01-31 Thread José Vázquez
2014-01-11, José Vázquez : > 2014/1/3, danitool : >> I'm also having these problems. The bug is very easy to reproduce. Just >> using the jffs2 image instead of squashfs, the problems are shown with >> the >> first boot, and you can see lot of funny names just listing /etc/init.d >> >> root@(none):

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-01-10 Thread José Vázquez
2014/1/3, danitool : > I'm also having these problems. The bug is very easy to reproduce. Just > using the jffs2 image instead of squashfs, the problems are shown with the > first boot, and you can see lot of funny names just listing /etc/init.d > > root@(none):/# ls -l /etc/init.d/ > -rwxr-xr-x

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2014-01-03 Thread danitool
I'm also having these problems. The bug is very easy to reproduce. Just using the jffs2 image instead of squashfs, the problems are shown with the first boot, and you can see lot of funny names just listing /etc/init.d root@(none):/# ls -l /etc/init.d/ -rwxr-xr-x1 root root 199

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-12-11 Thread José Vázquez
2013/12/5, José Vázquez : > I've enabled CPU_HOTPLUG in the kernel and added maxcpus=1 to the > CMDLINE. Once openwrt boot is finished i enable the second core. > https://www.kernel.org/doc/Documentation/cpu-hotplug.txt > The initial tests showed that the jffs2 problem doesn't happen, but > still m

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-12-05 Thread José Vázquez
2013/11/27, José Vázquez : > 2013/11/27, John Crispin : >> On 27/11/13 08:48, Florian Fainelli wrote: >>> >>> On Nov 26, 2013 11:42 PM, "John Crispin" >> > wrote: >>> > >>> > On 26/11/13 23:29, José Vázquez wrote: >>> >> >>> >> Maybe the problem is that part of the new

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-11-27 Thread José Vázquez
2013/11/27, John Crispin : > On 27/11/13 08:48, Florian Fainelli wrote: >> >> On Nov 26, 2013 11:42 PM, "John Crispin" > > wrote: >> > >> > On 26/11/13 23:29, José Vázquez wrote: >> >> >> >> Maybe the problem is that part of the new init process does not work >> >> wel

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-11-26 Thread John Crispin
On 27/11/13 08:48, Florian Fainelli wrote: On Nov 26, 2013 11:42 PM, "John Crispin" mailto:j...@phrozen.org>> wrote: > > On 26/11/13 23:29, José Vázquez wrote: >> >> Maybe the problem is that part of the new init process does not work >> well with two cpus:http://pastebin.com/LTUmbxZ6 > >

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-11-26 Thread Florian Fainelli
On Nov 26, 2013 11:42 PM, "John Crispin" wrote: > > On 26/11/13 23:29, José Vázquez wrote: >> >> Maybe the problem is that part of the new init process does not work >> well with two cpus:http://pastebin.com/LTUmbxZ6 > > > > who says the new init does not work on smp ? i would claim that bmips is

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-11-26 Thread John Crispin
On 26/11/13 23:29, José Vázquez wrote: Maybe the problem is that part of the new init process does not work well with two cpus:http://pastebin.com/LTUmbxZ6 who says the new init does not work on smp ? i would claim that bmips is just not supported properly and the maintainers of the code base

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-11-26 Thread José Vázquez
> > Finally decided to test with AA (kernel 3.3.8) for which i've made a > some kind of patch to enable SMP and nothing strange with jffs2 fs > happened. > Also noticed that bogomips in core 1 are the same that in core 0, > while with BB they are different: > http://pastebin.com/7jisa6km > http://p

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-11-25 Thread José Vázquez
2013/10/1, José Vázquez : >> Now i'm sure that only fails with smp images when block-mount is >> enabled, while with generic works fine. Also, with the Comtrend >> WAP-5813n (http://wiki.openwrt.org/toh/comtrend/ct5813) nobody noticed >> nothing strange because nobody enables block-mount in that ro

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-10-01 Thread José Vázquez
> Now i'm sure that only fails with smp images when block-mount is > enabled, while with generic works fine. Also, with the Comtrend > WAP-5813n (http://wiki.openwrt.org/toh/comtrend/ct5813) nobody noticed > nothing strange because nobody enables block-mount in that router. > What i can do to help

Re: [OpenWrt-Devel] bcm6368 + block-mount jffs2 problem.

2013-09-01 Thread Florian Fainelli
Hello, 2013/9/1 José Vázquez : > Each time i select block-mount some config files in /etc appeared > renamed after first reboot. The file content remains unchanged. > - Fresh install: > /etc/config: > 6relayd dropbear fstab network ucitrack wireless > dhcp firewall luci system