2008年6月14日 星期六
2007年4月21日 星期六
2007年4月19日 星期四
status of debian arm versatile qemu(4/19)
Applied my patches, I found
1. system work or kernel page error.
2. debian installation always work without kernel hang.
in that case, blue screen without anything.
3. I guess it is hardware model error.
But we need more systematic method to solve problem.
I try to debug by the follow steps.
First, I saw the kernel error in screen.
Because I use pyvnc2swf, I can saw all screen information in installation.
It show that
sym_evaluate_dp 0xa4/0x178
sym_compute_residual 0x78/0xe4
sym_interrupt 0xf0/0x18d8
sym53c8xx_intr 0x3c/0x6c
handle_IRQ_event 0x44/0x84
and then I use arm-elf-objdump -S to dump all of vmlinux > log
vmlinux has debug information, but vmlinuz not.
hence, you will get only assembly code if you dump vmlinuz.
and then you will find the memory error happen address in C code.
and then analysis these code
1. SYM_CONF_MAX_SG is 96. but (r0 = 0x1c8)
so that, some thing is wrong.
Another method is to enable debug mode in emulator,
and trace what happen inside. we can monitor all of transaction,
and find the problem.
for example above, we find the problem is happened in SCSI ISR.
Because of some mismatches, the ISR can not handle it correct.
1. system work or kernel page error.
2. debian installation always work without kernel hang.
in that case, blue screen without anything.
3. I guess it is hardware model error.
But we need more systematic method to solve problem.
I try to debug by the follow steps.
First, I saw the kernel error in screen.
Because I use pyvnc2swf, I can saw all screen information in installation.
It show that
sym_evaluate_dp 0xa4/0x178
sym_compute_residual 0x78/0xe4
sym_interrupt 0xf0/0x18d8
sym53c8xx_intr 0x3c/0x6c
handle_IRQ_event 0x44/0x84
and then I use arm-elf-objdump -S to dump all of vmlinux > log
vmlinux has debug information, but vmlinuz not.
hence, you will get only assembly code if you dump vmlinuz.
and then you will find the memory error happen address in C code.
and then analysis these code
1. SYM_CONF_MAX_SG is 96. but (r0 = 0x1c8)
so that, some thing is wrong.
Another method is to enable debug mode in emulator,
and trace what happen inside. we can monitor all of transaction,
and find the problem.
for example above, we find the problem is happened in SCSI ISR.
Because of some mismatches, the ISR can not handle it correct.
2007年4月12日 星期四
Debian Arm Versatile Qemu stability
- Always work
- without vnc viewer
- with vnc recoder pyvnc2swf
- with vnc viewer -viewonly
- Sometimes work
- remote vnc viewer
2007年4月10日 星期二
debian auto installation timeout
loop
sleep 10s
check the job status
if already wait 5000s
kill the job
else
continue wait
endloop
2007年4月8日 星期日
debian etch is released
my debian arm qemu version v2.8 is also released.(4/8)
Now, stability testing is running.
No, this version is not stable enough.(4/9)
apply vnc patch.
v3.0 is under testing.
v3.0 is work under 26 times continuous installation testing.(4/10 14:50)
v3.0 in ubuntu is under testing.(4/10 7:50)
v3.0 is also work under 6 times testing(4/10 14:50)
Now, stability testing is running.
No, this version is not stable enough.(4/9)
apply vnc patch.
v3.0 is under testing.
v3.0 is work under 26 times continuous installation testing.(4/10 14:50)
v3.0 in ubuntu is under testing.(4/10 7:50)
v3.0 is also work under 6 times testing(4/10 14:50)
2007年4月7日 星期六
qemu upstream
原先我們一直出新的patch給upstream用,以為qemu的upstream主要在穩定,但是系統太複雜,核心的patch會更動到所有的架構,今天來個irq patch, arm就不會動了,所以目前是給一個qemu cvs snapshot的版本,然後再上patch,這樣比較不會有問題啦........跟upstream還有點煩...
ps. 這個bug花點時間也找到了...
ps. 這個bug花點時間也找到了...
訂閱：
文章 (Atom)
