trouble with 1.15.2
walter harms
wharms at bfs.de
Wed Nov 25 16:56:02 UTC 2009
walter harms schrieb:
>
> Denys Vlasenko schrieb:
>> On Mon, Nov 9, 2009 at 9:08 AM, walter harms <wharms at bfs.de> wrote:
>>> Hi list,
>>> i have a strange problem with (most likely) ash.
>>> With 15.0 the system works fine. With 15.2 i start seeing additional(!) characters in
>> Does 1.15.1 work fine?
> not checked yet
>
>> Which patch exactly makes it not work?
>
> I could not bisect because i could not download the git source (no idea why, i have done it before)
>
>>> the output of linuxrc (kernel msg are fine), subsequent processes crash, system dead.
>> This bug description is too vague.
>> --
> i know, there idea was to ask if someone else had the same problem (sometimes i miss topics)
> I am very busy there days so i could not test 15.1 but here is the output of 15.2.
> The systems works fine with 15.0. this is a hexdump of the output.
> As you can see until 0003670 everything looks normal.
> but at the start of linuxrc you find: 8881
> Other 81 (and 88) are creeping in and some point later the whole system crashes.
> (not on capture here). BTW the script gets wrongly interpreted later.
> The think is reproduceable i see always these 818181 crap.
>
>
> 0003620: 204d 6f75 6e74 6564 2072 6f6f 7420 2863 Mounted root (c
> 0003630: 7261 6d66 7320 6669 6c65 7379 7374 656d ramfs filesystem
> 0003640: 2920 7265 6164 6f6e 6c79 2e0a 4672 6565 ) readonly..Free
> 0003650: 696e 6720 756e 7573 6564 206b 6572 6e65 ing unused kerne
> 0003660: 6c20 6d65 6d6f 7279 3a20 3430 6b20 6672 l memory: 40k fr
> 0003670: 6565 640a 8881 2f6c 696e 7578 7263 813a eed.../linuxrc.:
> 0003680: 204d 6f75 6e74 696e 6720 812f 6d6e 7481 Mounting ./mnt.
> 0003690: 2f66 6c61 7368 2e2e 2e20 8888 646f 6e65 /flash... ..done
> 00036a0: 880d 0a88 8188 8181 8188 8181 8181 8181 ................
> 00036b0: 8188 8181 8181 8181 8181 8181 8181 8181 ................
>
>
> note: i do not expect that anyone will debug this without help
> but i have no more time this weeks and perhaps someone else can reproduce that.
>
hi list,
i am still trying to find the bug but i noted something more disturbing.
With the move from 1.14.4 to 1.15.0 i found that my startup started sending a bunch
of 0 bytes to the terminal. This is gone unnoticed so far as that we do not see the hexvalues
of the startupmessages. (i used them to see the bug above).
It would be nice if someone would check that so i can get a second opinion.
I strongly suspect ash.c for the above behavior as that replacing the 1.15.2 ash.c with
1.15.1 restores the old bug. Please note that system look perfectly normal when you only
look at the ascii dump, i experience a crash only with 1.15.2.
I have still no idea if the bug is inside the toolchain or busybox.
re,
wh
example output: 1.15.0 with block of 0
0015f80: 653a 2035 2028 636c 6f63 6b20 6e6f 7420 e: 5 (clock not
0015f90: 7379 6e63 6872 6f6e 697a 6564 290d 0a00 synchronized)...
0015fa0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
......
0017e20: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0017e30: 0000 0000 0000 0000 0000 0000 2a2a 2a2a ............****
0017e40: 2a2a 2a2a 2a2a 2a2a 2a2a 2a2a 2a2a 2a2a ****************
More information about the busybox
mailing list