On 24.8.2012 1:49, Adam Hraska wrote:
> On Thu, Aug 23, 2012 at 1:21 PM, Jakub Jermar <[email protected]> wrote:
>> On 23.8.2012 9:56, Adam Hraska wrote:
>>> On Thu, Aug 23, 2012 at 12:45 AM, Jakub Jermar <[email protected]> wrote:
>>>> Tonight, I did some testing and unfortunately it appears the branch is
>>>> not that scrubbed or even tested as one would have hoped. These are the
>>>> issues I noticed:
>>>>
>>>> - test cht panics the kernel when run on real amd64 or ia32 hardware
>>>> (4-core Intel i5, 1.4GHz, 4G memory)
>>>> - test cht panics the kernel when run on the above machine in QEMU (-smp
>>>> 4 --enable-kvm)
>>>> - unfortunately the panic message is interleaved with some other
>>>> concurrent output so it is completely unreadable (some synchronization
>>>> should be probably added back to printf)
>>>
>>> That is very unfortunate. While I expected there to be some latent
>>> bugs in the implementation (as in any new software) I would not have
>>> expected "test cht" would fail (eg leak memory) and definitely not to
>>> panic.
>>>
>>> It is however quite difficult to respond to this point since I have no
>>> idea what went wrong.
>>
>> I believe this is the same thing as the QEMU panic on UP. The same
>> assertion is just hit by each CPU at about the same time, which would
>> explain the blended panic message.
> 
> Thanks. I will have a look at it on Sunday, when I get back to normal
> computer & internet connection.

Has there been any progress on this front? I was expecting at least the
major issues to be fixed rather soon. I would also like to submit
further comments while the memory is still fresh...

Jakub




_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel

Reply via email to