On Wed, 2011-03-30 at 15:13 +0200, Clemens Ladisch wrote:
Svante Signell wrote:
Code: f4 01 00 00 ef 31 f6 48 89 df e8 15 dd ff ff 85 c0 0f 88 2b 03 00 00 48 89 ef e8 ee 11 b9 e0 8b 7b 40 e8 9f 25 a7 e0 48 8b 43 38 <66> 8b 10 66 89 14 24 8b 43 14 83 e8 03 83 f8 01 77 32 31 d2 be
5: 31 f6 xor %esi,%esi 7: 48 89 df mov %rbx,%rdi a: e8 15 dd ff ff callq 0xffffffffffffdd24 f: 85 c0 test %eax,%eax 11: 0f 88 2b 03 00 00 js 0x342 17: 48 89 ef mov %rbp,%rdi 1a: e8 ee 11 b9 e0 callq 0xffffffffe0b9120d 1f: 8b 7b 40 mov 0x40(%rbx),%edi 22: e8 9f 25 a7 e0 callq 0xffffffffe0a725c6 27: 48 8b 43 38 mov 0x38(%rbx),%rax 2b: 66 8b 10 mov (%rax),%dx <-- crash here 2e: 66 89 14 24 mov %dx,(%rsp) 32: 8b 43 14 mov 0x14(%rbx),%eax 35: 83 e8 03 sub $0x3,%eax 38: 83 f8 01 cmp $0x1,%eax 3b: 77 32 ja 0x6f 3d: 31 d2 xor %edx,%edx
This is the azx_readw(chip, GCAP) in azx_create(); chip->remap_addr is 0xffffc90011c08000 which does look like a valid pointer, but isn't.
Thank you Clemens! Maybe your input is sufficient to solve this problem. I have now installed the debug version of the kernel, the objdump output is attached (please let me know if you are missing something).sorry, I don't know where to find the relevant information in this file, but that is all I have (still very large). (Does not include the error messages on stderr, maybe something is still missing.)
Thanks!