On Fri, 11 Feb 2000, Andrea Arcangeli wrote:
> On Fri, 11 Feb 2000, Manfred Spraul wrote:
>
> >He wrote that the process is stuck in __wait_on_buffer(), I'm not sure
> >if the semaphore deadlock detector will detect this.
>
> Sorry I didn't know. Thus new debugging way is suggested: enable kdb
> instead, press PAUSE and `btp xxx` where xxx is the pid of the deadlocked
> task.
>
I am trying to debug lowlatency-2.2.14-B1 + Linux-2.2.14aa7 with
"/bin/sync" stuck in D state. I applied 2.2.14-ikd1 and was able to solve
all FAILED hunks except in entry.S for the following code snippit:
-----part of entry.S.rej-------
testl $(VM_MASK),EFLAGS(%esp)
movl %esp,%eax
jne v86_signal_return
+ #ifndef CONFIG_KERNEL_DEBUGGING
xorl %edx,%edx
+ #else
+ pushl $0
+ pushl %eax
+ #endif
call SYMBOL_NAME(do_signal)
+ #ifdef CONFIG_KERNEL_DEBUGGING
+ addl $8,%esp
+ #endif
jmp restore_all
ALIGN
v86_signal_return:
+ #ifdef CONFIG_KERNEL_DEBUGGING
+ pushl %eax
+ #endif
call SYMBOL_NAME(save_v86_state)
movl %eax,%esp
+ #ifndef CONFIG_KERNEL_DEBUGGING
xorl %edx,%edx
+ #else
+ pushl $0
+ pushl %eax
+ #endif
call SYMBOL_NAME(do_signal)
+ #ifdef CONFIG_KERNEL_DEBUGGING
+ addl $8,%esp
+ #endif
jmp restore_all
-----end entry.S.rej snippit------
I think I can fix the FAILED hunk but I would feel more confident
if I knew what this code was doing. Can you give a brief explanation of
the ikd additions in this area?
Wm
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:30 EST